Preventions
- Home
- - Preventions
- -PV077
- ID: PV077
- Created: 22nd October 2025
- Updated: 22nd October 2025
- Contributor: David Larsen
Controlled Software Inventory Management
Maintain a centralized, enforceable inventory of all software permitted for use on enterprise-managed systems. Unauthorized or unmanaged software increases the risk of tool misuse, data movement, lateral exploitation, and unmonitored communication, each of which may enable or conceal insider activity.
A software inventory is not passive documentation; it is a dynamic enforcement boundary. Effective control requires both technical constraint (e.g., allowlisting) and structured visibility into what applications are deployed, by whom, and for what purpose.
Key Prevention Measures
- Deploy endpoint management platforms capable of full software inventory visibility, such as Microsoft Intune, JAMF (macOS), Tanium, CrowdStrike Falcon, or ManageEngine Endpoint Central.
- Enforce application allowlisting using tools like Microsoft Defender Application Control (WDAC), AppLocker, or third-party EDR integrations.
- Maintain a centralized, queryable list of all approved applications, including version ranges, installation context (user vs. system), and business justification.
- Log every software install event with metadata including hostname, username, install timestamp, and installation method.
- Require all application installations to originate from approved enterprise repositories or deployment platforms (e.g., SCCM, Intune, JAMF).
- Prohibit local administrator rights for population members except under time-limited, auditable exceptions.
- Detect and flag installation of encryption tools, anonymizers, remote desktop clients, or developer toolchains on non-technical endpoints.
- Conduct monthly reconciliations between installed applications and the approved software list, using EDR or inventory tools.
- Investigate installation of communication platforms not sanctioned by enterprise IT (e.g., Signal, Telegram Desktop, third-party file transfer clients).
- Automatically remove or isolate endpoints found running prohibited software, and require investigation before rejoining corporate networks.
Investigator Considerations
- Software inventory logs are a high-value artifact for understanding preparatory behavior, such as staging exfiltration tools or side-channel communication clients.
- Discrepancies between allowed software and observed installations often indicate circumvention of standard IT channels.
- Repeated installations of the same unapproved tool across multiple devices or subjects may reflect behavioral drift or informal tool adoption within a team.
- Software changes shortly before a known incident window may indicate staging activity, particularly if correlated with anomalous file or network activity.
Sections
| ID | Name | Description |
|---|---|---|
| IF009 | Installing Unapproved Software | A subject installs software onto an organization-managed system without prior approval or outside sanctioned methods (e.g., centralized package management, internal software portals). This behavior spans a spectrum of risk - from seemingly benign installations (e.g., video games, personal browsers, media players) to unauthorized deployment of potentially harmful tools sourced from unvetted repositories or adversarial infrastructure.
The infringement may involve:
While some installations may appear harmless, unapproved software installs can represent a breakdown in configuration control and acceptable use. In high-risk scenarios, such software may introduce remote access mechanisms, data exfiltration capabilities, or other malware. Even benign cases signal behavioral drift, particularly when repeated or ignored, and can contribute to software sprawl, policy erosion, or eventual exploitation. |
| IF034 | Exfiltration via Automated Transcription | Exfiltration via automated transcription refers to the capture and conversion of spoken information into structured, persistent data through the use of transcription technologies, including AI-enabled note-taking tools, meeting assistants, and speech-to-text systems.
Unlike traditional media capture techniques, this behavior does not merely reproduce information, it transforms ephemeral verbal communication into searchable, shareable, and analyzable content. This significantly increases the utility and scalability of exfiltrated data, enabling subjects to accumulate large volumes of sensitive information over time with minimal manual effort.
This technique may occur using external tools operating outside organizational control or through misuse of approved or embedded transcription capabilities within enterprise platforms. As a result, it spans both out-of-band and in-band exfiltration paths, making it distinct from media capture behaviors.
In addition to software-based transcription tools, subjects may leverage dedicated or repurposed hardware to capture audio streams for later transcription or processing. This includes the use of intermediary devices capable of intercepting microphone input or headphone output, such as inline audio capture adapters, modified peripherals, or secondary recording devices connected to audio interfaces.
These methods enable the subject to capture high-quality audio directly from system inputs or outputs without relying on visible applications or introducing detectable software artifacts. In such cases, audio may be recorded covertly and later processed through transcription tools outside the organizational environment, further separating the point of capture from the point of transformation and exfiltration.
Exfiltration via automated transcription is particularly effective in environments where sensitive information is frequently communicated verbally, including strategic discussions, incident response, legal proceedings, and technical collaboration. The presence of this behavior may indicate deliberate collection of high-value conversational intelligence, especially where transcription outputs are retained, aggregated, or transferred beyond approved boundaries.
From an investigative perspective, this technique introduces a shift from event-based capture to continuous collection, where subjects build structured datasets over time. Detection therefore relies on identifying tool usage, data flows, and the presence of generated artifacts, rather than isolated capture events. |
| IF009.005 | Anti-Sleep Software | The subject installs or enables software, scripts, or hardware devices designed to prevent systems from automatically locking, logging out, or entering sleep mode. This unauthorized action deliberately subverts security controls intended to protect unattended systems from unauthorized access.
Characteristics
Example ScenarioA subject installs unauthorized anti-sleep software on a corporate laptop to prevent automatic locking during idle periods. As a result, the device remains accessible even when left unattended in unsecured environments such as cafes, airports, or shared workspaces. This action bypasses mandatory screen-lock policies and renders full disk encryption protections ineffective, exposing sensitive organizational data to theft or compromise by malicious third parties who can physically access the unattended device. |
| IF009.002 | Inappropriate Software | A subject installs software that is not considered appropriate by the organization. |
| IF009.007 | Installation of Unapproved Browser Extensions | The subject installs browser extensions on a managed device that have not been approved, vetted, or distributed via sanctioned organizational channels. These may include productivity tools, automation agents, data scrapers, content manipulators, or AI-enhanced interfaces. Installations typically originate from GitHub repositories, private developer sites, shared file storage, or sideloading tools that bypass enterprise browser controls.
Unapproved extensions introduce unmonitored execution environments directly into the subject’s browser, enabling silent access to sensitive web applications, stored credentials, and internal content. Many request expansive permissions (e.g.,
This behavior violates Acceptable Use Policies and, depending on the extension’s behavior, may also constitute unauthorized access, data exfiltration, or malware introduction. Some extensions—particularly those hosted on GitHub or distributed through Telegram groups or developer forums—have been found to contain obfuscated payloads, embedded credential harvesters, or cryptojacking modules.
Examples include:
While subjects may initially claim curiosity or productivity needs, repeated installation of unapproved extensions—especially after prior enforcement—may indicate normalization of risky behavior or active circumvention of controls. |
| IF009.006 | Installing Crypto Mining Software | The subject installs and operates unauthorized cryptocurrency mining software on organizational systems, leveraging compute, network, and energy resources for personal financial gain. This activity subverts authorized system use policies, degrades operational performance, increases attack surface, and introduces external control risks.
Characteristics
Example ScenarioA subject installs a customized |
| IF009.001 | Unwanted Software | A subject installs software that is not inherently malicious, but is not wanted, commonly known as “greyware” or “potentially unwanted programs”. |