Detection: Cisco Duo Policy Allow Tampered Devices

Updated Date: 2025-07-10 ID: 6b813efd-8859-406f-b677-719458387fac Author: Patrick Bareiss, Splunk Type: TTP Product: Splunk Enterprise Security

Description

The following analytic detects when a Duo policy is created or updated to allow tampered or rooted devices, such as jailbroken smartphones, to access protected resources. It identifies this behavior by searching Duo administrator activity logs for policy changes where the allow_rooted_devices setting is enabled. This is accomplished by filtering for policy creation or update actions and parsing the policy description for the relevant configuration. Allowing tampered devices poses a significant security risk, as these devices may bypass built-in security controls, run unauthorized software, or be more susceptible to compromise. For a Security Operations Center (SOC), identifying such policy changes is critical because it may indicate either a misconfiguration or a malicious attempt to weaken authentication requirements, potentially enabling attackers to access sensitive systems with compromised devices. The impact of this attack can include unauthorized access, data breaches, and lateral movement within the environment, making prompt detection and response essential to maintaining organizational security.

Search

1`cisco_duo_administrator` action=policy_update OR action=policy_create 
2| spath input=description 
3| search allow_rooted_devices=true 
4| rename object as user 
5| stats count min(_time) as firstTime max(_time) as lastTime by action actionlabel description user admin_email 
6| `security_content_ctime(firstTime)` 
7| `security_content_ctime(lastTime)` 
8| `cisco_duo_policy_allow_tampered_devices_filter`

Data Source

Name	Platform	Sourcetype	Source
Cisco Duo Administrator	N/A	`'cisco:duo:administrator'`	`'cisco_duo'`

Macros Used

Name	Value
cisco_duo_administrator	`sourcetype=cisco:duo:administrator`
cisco_duo_policy_allow_tampered_devices_filter	`search *`

cisco_duo_policy_allow_tampered_devices_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1556	Modify Authentication Process	Credential Access

Exploitation

Installation

DE.CM

CIS 10

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Notable	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Risk Event	True

This configuration file applies to all detections of type TTP. These detections will use Risk Based Alerting and generate Notable Events.

Implementation

The analytic leverages Duo activity logs to be ingested using the Cisco Security Cloud App (https://splunkbase.splunk.com/app/7404).

Known False Positives

unknown

Associated Analytic Story

Cisco Duo Suspicious Activity

Risk Based Analytics (RBA)

Risk Message:

A policy has been created or updated to allow tampered devices by user $user$ with email $admin_email$

Risk Object	Risk Object Type	Risk Score	Threat Objects
user	user	48	No Threat Objects

References

https://splunkbase.splunk.com/app/7404

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	✅ Passing	N/A	N/A	N/A
Unit	✅ Passing	Dataset	`duo`	`cisco:duo:administrator`
Integration	✅ Passing	Dataset	`duo`	`cisco:duo:administrator`

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 1