ac-7-2-purge-or-wipe-mobile-device

name	AC-7(2)_purge-or-wipe-mobile-device
description	Purge or wipe information from [organization-defined] based on [organization-defined] after [organization-defined] consecutive, unsuccessful device lo
category	authorization
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ac-7-2","ac","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-284"]
chains_with	["AC-19","MP-5","MP-6"]
prerequisites	["AC-7"]
severity_boost	{"AC-19":"Chain with AC-19 for comprehensive security coverage","MP-5":"Chain with MP-5 for comprehensive security coverage","MP-6":"Chain with MP-6 for comprehensive security coverage"}

AC-7(2) Purge or Wipe Mobile Device

Enhancement of: AC-7

High-Level Description

Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5

A mobile device is a computing device that has a small form factor such that it can be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable or removable data storage; and includes a self-contained power source. Purging or wiping the device applies only to mobile devices for which the organization-defined number of unsuccessful logons occurs. The logon is to the mobile device, not to any one account on the device. Successful logons to accounts on mobile devices reset the unsuccessful logon count to zero. Purging or wiping may be unnecessary if the information on the device is protected with sufficiently strong encryption mechanisms.

What to Check

• Verify AC-7(2) Purge or Wipe Mobile Device is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for AC-7(2)
• Verify enhancement builds upon base control AC-7

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AC-7(2) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check IAM policies and access controls	cloud_audit_iam_policies
hackbrowser-mcp	Test web application access controls	browser_auth_test

Remediation Guide

Control Statement

Purge or wipe information from [organization-defined] based on [organization-defined] after [organization-defined] consecutive, unsuccessful device logon attempts.