preventions
- ID: PV085
- Created: 25th March 2026
- Updated: 25th March 2026
- Contributor: The ITM Team
Multi-Party Approval Enforcement
Multi-party approval enforcement requires that designated high-risk or sensitive actions undergo validation by two or more independent approvers before execution. This control ensures that no single subject can unilaterally authorize actions that carry elevated operational, financial, or security impact.
Sensitive actions should be clearly defined and may include privilege elevation, financial transactions above defined thresholds, production changes, access to restricted data, or policy exceptions. Approval must be enforced at the system level, preventing execution unless all required approvals are obtained.
To maintain effectiveness, approvers must be independent of the requesting subject, with separation enforced through role design, reporting lines, or system constraints. Approval chains should not be user-selectable where possible, and must be resistant to manipulation or bypass.
This control directly mitigates behaviors associated with oversight degradation by introducing mandatory independent validation, reducing the likelihood that actions can proceed without scrutiny or through unilateral influence.
Sections
| ID | Name | Description |
|---|---|---|
| PR037 | Oversight Circumvention and Control Degradation | A subject weakens, bypasses, or manipulates oversight mechanisms designed to enforce validation, accountability, and governance over sensitive actions. These mechanisms include peer review processes, approval workflows, and segregation of duties, which collectively function to detect error, prevent misuse, and ensure independent verification.
This behavior does not constitute harm in itself but modifies the control environment in advance of an infringement, reducing the likelihood that subsequent actions are scrutinized, challenged, or blocked. |
| IF033 | Digital Defacement | Digital defacement occurs when a subject deliberately alters, replaces, or manipulates content across organizational digital assets without authorization. This includes public-facing platforms such as corporate websites and social media profiles, as well as internal systems such as intranet portals, knowledge bases, or collaboration environments.
The behavior is characterized by the compromise of trusted communication channels, where legitimate content is modified to display unauthorized messaging, misleading information, or reputationally damaging material. In some cases, defacement may be overt and disruptive; in others, it may be subtle, designed to misinform, undermine trust, or facilitate further insider activity. |
| PR046 | System Persistence | The subject modifies a system, application, or operating environment to preserve unauthorized access, execution, or control beyond the initial activity. The persistence mechanism is intended to remain available following events that would ordinarily interrupt the subject’s access, including system restart, user logoff, application termination, credential changes, or the subject’s departure from the organization.
System persistence may be established through the creation or modification of scheduled tasks, cron jobs, system services, startup items, Registry autorun locations, login scripts, systemd units, Windows Management Instrumentation event subscriptions, SSH authorized keys, web shells, application extensions, or other automatically executed components. The subject may create a new persistence mechanism or alter an existing legitimate component so that unauthorized code, commands, or remote-access functionality is invoked without requiring repeated manual action.
This behavior is preparatory where the subject establishes the mechanism before an intended infringement, allowing access or execution to continue at a later time or under conditions in which the subject’s normal account is unavailable. Persistence may support subsequent unauthorized access, data collection, sabotage, surveillance, or execution by another party. |
| IF040 | Data Integrity Manipulation | The subject inserts, deletes, alters, substitutes, suppresses, or misrepresents organizational data in a manner that compromises its accuracy, completeness, authenticity, or reliability. The manipulation may affect stored records, data moving between systems, or information generated and presented while an application is operating.
Data integrity manipulation may be intended to influence a business process, conceal activity, mislead stakeholders, obtain personal benefit, cause operational harm, or undermine organizational decision-making. Affected information may include financial records, customer data, operational measurements, transactions, case records, communications, database entries, system outputs, or other information relied upon by the organization. |
| AF043 | Physical Destruction of Evidence | A subject deliberately destroys or materially damages a physical item to prevent or hinder its examination, the recovery of information it contains, or its use in establishing relevant events. The behavior may target electronic devices, storage media, paper records, handwritten notes, or other physical material with evidentiary value. The subject may perform the destruction directly or arrange for another person or service to carry it out, including by misusing an otherwise legitimate disposal process.
The behavior may occur before an investigation begins or after the subject becomes aware of scrutiny. The item does not need to have been formally identified or collected as evidence, and complete destruction or successful prevention of recovery is not required. Classification requires evidence that the destruction was intended to conceal relevant activity or frustrate investigation. Accidental damage, routine authorized disposal, or an unexplained missing item does not independently establish this behavior. |
| PR054 | Record Export | A subject uses reporting, query, or export functions to generate a separately usable copy of records held within an organizational application or database in preparation for an infringement. The subject may run an existing report, select particular fields or record populations, expand reporting parameters, or perform repeated exports to assemble the required information. The records may concern customers, personnel, financial transactions, cases, or other organizational activity. The resulting extract may be retained as a report, spreadsheet, data file, or saved dataset, including within an organizational system without being downloaded to the subject’s device.
The defining behavior is the production of a record-level extract from underlying application or database content, rather than the retrieval of pre-existing files. The subject may use legitimately assigned permissions without circumventing a technical control. Investigators should establish which records and fields were included, whether the output was successfully generated and retained, and how its creation relates to the subject’s responsibilities, approved tasks, and subsequent activity. Possession of export permissions, creation of a report definition, or ordinary viewing of records does not independently establish this behavior. An export’s size or sensitivity alone does not establish preparation for an infringement. |
| PR037.001 | Oversight Control Bypass | A subject executes an action without undergoing required oversight by circumventing, disabling, or otherwise avoiding established approval or validation controls.
This includes actions that bypass mandatory review, approval, or authorization steps that are designed to ensure independent verification before an action is completed. Examples include directly executing controlled actions without triggering required approvals, self-authorizing where independent approval is mandated, or exploiting gaps that allow actions to proceed outside defined control pathways.
The defining characteristic of this behavior is that the oversight mechanism is not engaged at all, resulting in a complete absence of independent scrutiny.
Oversight control bypass undermines critical governance structures intended to prevent unauthorized, erroneous, or harmful activity. By removing these control points, the subject creates conditions in which actions can be performed without challenge, increasing the likelihood that subsequent infringement occurs undetected. |
| PR037.005 | Reviewer Collusion or Reciprocity | A subject engages in coordinated behavior with one or more individuals to ensure approval of actions without meaningful scrutiny.
This includes reciprocal approval arrangements, patterned interactions where individuals consistently approve each other’s actions, or implicit agreements to avoid challenge or escalation. The behavior may be explicit or emerge over time through repeated interaction patterns, resulting in a breakdown of independent validation.
The defining characteristic of this behavior is multi-subject coordination, where oversight is degraded through collective alignment rather than unilateral action.
Although formal review or approval processes remain in place, their integrity is compromised by the absence of genuine independence. Over time, this behavior can normalize superficial validation practices within a group, embedding weakened oversight into routine operations and increasing exposure to undetected infringement. |
| PR037.002 | Review Condition Manipulation | A subject influences the human conditions under which review occurs to reduce scrutiny or increase the likelihood of approval.
This includes strategic selection of reviewers, timing of submissions to coincide with reduced staffing or attention, or structuring work in a manner that limits reviewer engagement or visibility. The subject acts unilaterally to shape who reviews, when review occurs, and how attention is applied, without altering the formal workflow itself.
The review process remains intact in form, but its effectiveness is degraded through contextual manipulation. This creates an appearance of compliance while reducing the likelihood that issues are identified or challenged. |
| PR037.004 | Approval Workflow Exploitation | A subject exploits weaknesses, gaps, or edge cases within formal approval workflows to obtain authorization with reduced scrutiny, while remaining within the defined process.
This includes manipulating workflow conditions such as approval thresholds, conditional routing logic, exception handling paths, or automated approval mechanisms. The subject leverages the rules and structure of the workflow itself, enabling actions to progress through approval channels with minimal or superficial validation.
The defining characteristic of this behavior is that the oversight mechanism is engaged, but its effectiveness is reduced through exploitation of process logic.
Although the subject appears to comply with formal procedures, the intent of the control is undermined. Actions that would typically require independent review or deeper scrutiny are approved with limited challenge, increasing the risk of unauthorized or harmful outcomes. |
| PR037.003 | Segregation of Duties Circumvention | A subject consolidates control authority by obtaining, retaining, or exploiting permissions that allow them to perform multiple stages of a controlled process without independent oversight.
This includes scenarios where the subject holds or acquires overlapping roles that are intended to remain separate, such as the ability to request and approve actions, initiate and authorize transactions, or develop and deploy changes. The behavior may arise from misconfigured access controls, privilege accumulation over time, or informal deviations from defined role boundaries.
The defining characteristic of this behavior is the structural collapse of role separation, where control mechanisms designed to enforce independence are no longer effective.
By eliminating separation between responsibilities, the subject creates conditions in which actions can be completed without challenge or verification. This removes a foundational safeguard against error, misuse, and unauthorized activity, significantly increasing the likelihood that subsequent infringement can occur undetected. |
| IF033.001 | Public Website Defacement | A subject alters or replaces content on externally accessible organizational websites without authorization. This may include homepage takeovers, modified text or imagery, injected messages, or redirection to external domains. The behavior typically targets high-visibility assets and is often designed to be immediately noticeable to customers, partners, or the general public.
Public website defacement is frequently used to signal grievance, ideological positioning, or dissatisfaction, but may also serve as a precursor or distraction for other malicious activity. The impact extends beyond the technical compromise, affecting brand perception, stakeholder confidence, and potentially triggering regulatory or contractual consequences depending on the nature of the content displayed. |
| IF033.002 | Social Media Profile Defacement | A subject gains control of, or misuses legitimate access to, official organizational social media accounts to post, modify, or remove content without authorization. This includes publishing unauthorized messages, altering profile information such as names, bios, or images, and deleting legitimate communications. The behavior leverages the speed and reach of social platforms to rapidly influence public perception.
Unlike traditional defacement, this activity may blend into normal operational use, making attribution and detection more challenging. The subject may post misleading, inflammatory, or false information, creating confusion among followers and stakeholders. The resulting impact can include reputational damage, misinformation propagation, and loss of trust in official communication channels. |
| IF033.003 | Intranet Defacement | A subject modifies content within internal-facing platforms such as intranet portals, employee dashboards, or internal web services without authorization. This may involve altering announcements, internal communications, or shared resources that the organizational population relies on for accurate information.
Although not publicly visible, intranet defacement can have significant operational consequences. The subject may introduce misleading or false information that disrupts workflows, causes confusion, or undermines confidence in internal systems. |
| IF033.004 | Internal Knowledge Base and Documentation Tampering | A subject alters content within internal knowledge repositories, including wikis, technical documentation, runbooks, or policy libraries. These modifications may appear legitimate at a glance but introduce inaccuracies, omissions, or misleading instructions that affect how tasks are performed across the organization.
This form of defacement is often subtle and persistent, making it difficult to detect without version control analysis or user reporting. The impact is typically operational rather than immediate, degrading process integrity, increasing the likelihood of errors, and potentially introducing security or compliance risks through the use of compromised guidance. |
| PR046.001 | Scheduled Execution | The subject creates or modifies a scheduled task, cron job, system timer, or equivalent mechanism to execute unauthorized commands or code automatically at a future time or recurring interval. |
| PR046.004 | Event-Triggered Execution | The subject creates or modifies an event subscription, event handler, system hook, or equivalent trigger that executes unauthorized commands or code when specified conditions are met. |
| PR046.005 | SSH Authorized Key Modification | The subject adds, replaces, or modifies a Secure Shell (SSH) authorized key or related trust configuration to preserve unauthorized remote access to a system, virtual machine, hypervisor, or network device. |
| PR046.009 | Server Software Component Modification | The subject installs or modifies an extensible server component, stored procedure, transport agent, server module, service library, or virtualization package to preserve unauthorized execution or access.
This Sub-section excludes web shells, which are represented separately under PR046.006 – Web Shell Deployment. |
| PR046.010 | Boot or Firmware Modification | The subject modifies a bootloader, boot image, boot partition, firmware component, Unified Extensible Firmware Interface configuration, or network-device boot mechanism to preserve unauthorized execution or control. |
| PR047.003 | Centralized Management Platform Access | The subject uses a cloud control plane, software deployment system, endpoint-management platform, configuration-management service, or orchestration tool to access, manage, or execute actions on additional organizational systems outside an approved operational requirement. |
| PR024.002 | Privilege Activation | The subject activates elevated permissions that are assigned to them or conditionally available through an established organizational or operating-system mechanism. This may include
The activation may itself be approved or unapproved. It should be recorded where entering the elevated context is materially relevant to an investigation, including where an approved mechanism is used outside its authorized purpose or before a later infringement. |
| PR024.004 | Authorization Attribute Manipulation | The subject creates or modifies an identity, directory, group, role, token, or authorization attribute so that an account or process receives permissions beyond its normal access context. This may include introducing privileged Security Identifier History values, modifying group or role assignments, or altering identity attributes that are evaluated during authorization.
The change may be made through an approved administrative interface or through unauthorized technical manipulation. |
| IF040.001 | Stored Record Manipulation | The subject inserts, deletes, alters, substitutes, or suppresses data retained within an organizational system so that the authoritative record becomes inaccurate, incomplete, misleading, or unreliable.
Affected information may include database entries, business records, documents, stored communications, transactions, customer records, inventory values, measurements, or case information. |
| IF016.012 | Fraudulent Refund Issuance | A subject abuses authorized access to create, approve, increase, duplicate, or redirect a refund without a legitimate business basis or required authorization.
The subject may issue the refund to themselves, a friend, family member, associate, colluding customer, or another external party. This may involve refunding a transaction that did not occur, issuing a refund where the goods or services remain valid, refunding more than the original amount, processing the same refund multiple times, or redirecting the proceeds to a payment method or account controlled by an unauthorized recipient.
The subject may conceal the infringement by creating fictitious customer complaints, manipulating return or cancellation records, using unrelated customer accounts, bypassing approval thresholds, dividing the value across multiple refunds, or recording false reasons for the transaction. |
| IF016.011 | Misappropriation of Redeemable Value | A subject abuses authorized access to create, issue, increase, transfer, or redeem value-bearing instruments or account-based benefits without a legitimate business purpose or required approval.
Redeemable value may include gift cards, promotional codes, vouchers, account credits, loyalty balances, refund credits, service credits, or similar benefits that can be exchanged for goods, services, discounts, or financial advantage.
The subject may direct the value to themselves, friends, family members, associates, colluding customers, or other external parties. The value may be provided without payment, sold, exchanged, or otherwise used for personal or third-party gain.
The subject may conceal the activity by using fictitious justifications, linking issuance to unrelated customer records, splitting value across multiple low-value transactions, remaining below approval thresholds, or repeatedly reissuing credits or codes. |
| IF043.001 | Personnel Diversion | A subject directs organizational personnel to perform work for an unauthorized purpose, beneficiary, or activity. Harm may include lost working time, delayed tasks, increased labour cost, or reduced operational capacity. |
| IF043.003 | Equipment or Facility Diversion | A subject redirects organizational equipment, vehicles, facilities, laboratories, production capability, or other physical assets toward an unauthorized use. Harm may include reduced availability, damage, operating cost, or disruption to legitimate activity. |
| IF043.004 | Inventory Diversion | A subject redirects organizational stock, materials, products, components, or consumable assets to an unauthorized recipient, destination, or purpose. Harm may include financial loss, stock discrepancies, supply shortages, or production delays. |
| IF044.005 | Unauthorized Waiver or Control Exception | A subject improperly waives, bypasses, suspends, or grants an exception to a mandatory organizational control using authority available through their role.
Examples include:
|
| IF016.013 | Expense Reimbursement Fraud | A subject submits, alters, duplicates, or knowingly misrepresents an expense claim to obtain reimbursement for costs that were not legitimately incurred for an authorized organizational purpose. This may include fabricated receipts, inflated amounts, duplicate submissions, personal purchases presented as business expenses, false mileage or subsistence claims, and expenses already reimbursed through another channel.
The infringement may involve a single material claim or a repeated pattern of lower-value claims designed to remain below approval or audit thresholds. |
| MT021.001 | Conflicting Personal Relationship | A subject is influenced by a personal, familial, romantic, or close social relationship with an individual whose interests are affected by the subject’s organizational responsibilities.
The relationship may involve a colleague, applicant, customer, supplier representative, contractor, investigation subject, complainant, or another person connected to an organizational decision. The conflict may arise where the subject can approve access, influence recruitment, award work, alter a case outcome, disclose information, suppress scrutiny, or provide another form of preferential treatment.
The existence of a personal relationship does not itself establish harmful intent. The investigative concern arises where the relationship creates a material conflict with the subject’s duties and is not disclosed through the organization’s required process. Relevant indicators may include repeated favorable decisions, unusual access to information concerning the connected person, involvement in matters from which the subject should have recused themselves, or communications inconsistent with the stated professional relationship.
Investigators should establish the nature and timing of the relationship, the subject’s disclosure obligations, the decisions or access affected by it, and whether the subject took steps to conceal the connection. The resulting infringement may separately involve abuse of decision-making authority, unauthorized data access, data disclosure, fraud, or interference with an investigation. |
| MT021.002 | Conflicting Financial Interest | A subject holds an undisclosed financial interest in an organization, individual, transaction, investment, asset, or commercial outcome affected by their organizational responsibilities.
The interest may include company ownership, shares, debt, commission, referral payments, profit-sharing arrangements, creditor relationships, beneficial ownership, or another financial position through which the subject may gain or avoid loss. The interest may be held directly or indirectly through a family member, associate, trust, company, or other intermediary.
The conflict becomes operationally significant where the subject can influence procurement, supplier selection, pricing, investment decisions, contract awards, customer treatment, regulatory review, access permissions, or the handling of confidential information. The subject may favor a connected entity, suppress unfavorable information, disclose commercially useful material, or manipulate a decision while presenting their actions as ordinary professional judgment.
Investigators should identify the financial relationship, determine when it began, establish whether disclosure was required, and compare the subject’s decisions with objective organizational criteria. Evidence may include corporate ownership records, declared-interest registers, procurement records, payment data, communications, approval history, and repeated decisions benefiting the same external entity. |
| AF013.005 | Delete Cloud User Account | A subject deletes a cloud user account to conceal activity, disrupt attribution, remove access associations, interfere with an investigation, or remove information connected to the account. The deleted identity may be maintained within a cloud platform, cloud identity provider, or Software as a Service application and may include a member or guest account.
Deletion may be performed through an administration portal, command-line interface, Application Programming Interface (API), script, or automated identity-lifecycle workflow. Investigators should identify the initiating subject, target identity, deletion method, source address, privileged role used, approval record, and deletion time. They should also preserve and review the account’s prior authentication activity, group and role memberships, authentication methods, licenses, owned resources, mailbox or storage data, and recovery status. Cloud identity platforms retain audit records capable of identifying changes to users and other directory objects, while services such as AWS CloudTrail record account activity involving the creation, modification, or deletion of Identity and Access Management resources.
Routine account deletion performed through an authorized offboarding or identity-governance process should not be classified as anti-forensic activity. Classification should require evidence that the deletion was unauthorized, concealed, inconsistent with the approved lifecycle process, or intended to frustrate attribution or preservation. |
| AF043.003 | Physical Destruction of Paper Records | A subject deliberately destroys or materially damages paper records to prevent or hinder their examination or their use in establishing relevant events. The records may include original organizational documents, printed copies, handwritten notes, notebooks, correspondence, or paper-based transaction records. The subject may perform the destruction directly or arrange for another person or service to carry it out, including by introducing relevant records into an otherwise legitimate disposal process.
The behavior includes destruction of complete records or selected portions containing relevant information. It may occur before an investigation begins or after the subject becomes aware of scrutiny. Complete destruction or successful prevention of recovery is not required. Classification requires evidence that the destruction was intended to conceal relevant activity or frustrate investigation; routine authorized disposal, accidental damage, or an unexplained missing record does not independently establish the behavior. |
| AF043.004 | Physical Destruction of Electronic Devices | A subject deliberately destroys or materially damages an electronic device to prevent or hinder its examination or the recovery of information relevant to the subject’s activity. The behavior may target organizational or personally owned laptops, desktop computers, smartphones, tablets, recording devices, or other electronic equipment used in the relevant activity. The subject may perform the destruction directly or arrange for another person or service to carry it out.
This Sub-section concerns destruction directed at the device as a complete item, rather than a separately targeted storage component. The damage may impair access to information without rendering every component unusable, and successful prevention of recovery is not required. Classification requires evidence connecting the damage to an intention to conceal relevant activity or frustrate investigation. Accidental damage, ordinary hardware failure, authorized disposal, or loss of device connectivity does not independently establish the behavior. |
| IF016.014 | Acceptance of Bribes or Kickbacks | A subject knowingly accepts money or another financial or material benefit in exchange for misusing entrusted access, information, authority, or an organizational process. The benefit may be received directly or provided to another person or entity at the subject’s direction. The arrangement may involve favorable supplier selection, approval of improper payments, unauthorized disclosure of information, provision of access, or circumvention of an organizational requirement. The benefit may be provided before or after the associated misuse as part of the arrangement.
The defining behavior is the knowing acceptance of a benefit linked to the misuse of the subject’s organizational role, rather than the source of the payment or whether organizational funds were directly diverted. Investigators should establish the benefit, its provider and intended beneficiary, the associated request or agreement, and the relevant organizational actions. An offered inducement that the subject refuses, an unexplained payment, or an authorized gift does not independently establish this behavior. Acceptance of the benefit and completion of the associated misuse should be established separately. |
| PR055.001 | Insider Collaborator Recruitment | A subject seeks to recruit another person who currently has, or previously had, authorized access to the affected organization’s resources to knowingly assist an infringement or its concealment. The requested assistance may draw on that person’s access, organizational knowledge, decision-making authority, operational responsibilities, or trusted relationships. This may involve obtaining restricted information, providing credentials or physical entry, approving improper transactions, making unauthorized changes, suppressing scrutiny, or recruiting additional participants.
The person approached may be a colleague, manager, direct report, former member of the organization, or trusted third-party personnel. Investigators should establish the person’s relationship with the organization, the assistance sought, and whether the subject communicated its unauthorized purpose. Recruitment of a former member does not establish that they retain access, and recruitment of a privileged individual does not establish that their privileges were subsequently used. A managerial instruction or request for assistance should not be treated as knowing recruitment solely because it later contributes to an infringement. |
| PR055.002 | External Collaborator Recruitment | A subject seeks to recruit a person outside the affected organization’s current or former authorized-access population to knowingly assist an infringement or its concealment. The requested assistance may involve identifying or acting as a buyer for organizational information, arranging unauthorized transactions, supplying technical capabilities, providing infrastructure, introducing further participants, or receiving and handling information, assets, or proceeds. The subject may approach an existing personal or professional contact, seek an introduction through an intermediary, or contact a previously unknown person.
The distinguishing feature is the recruitment of external participation in the unauthorized activity, rather than ordinary engagement with an external service provider or information recipient. Investigators should establish the role proposed, the improper purpose communicated, the person’s response, and any agreed terms or subsequent assistance. A person who unknowingly provides an otherwise legitimate service should not be classified as a recruited collaborator. Contact with an external party, an introduction, or an unexplained payment does not independently establish recruitment. |