Track processing purposes of personally identifiable information using [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill PT-3(2)_automation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of PT 3(2) Automation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-pt-3-2-automation)More formats (shields.io, HTML) on the badges page.
---
name: "PT-3(2)_automation"
description: "Track processing purposes of personally identifiable information using [organization-defined]."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- pt-3-2
- pt
- enhancement
tech_stack:
- any
cwe_ids:
- CWE-359
chains_with:
- CA-6
- CM-12
- PM-5
- PM-22
- SC-16
- SC-43
- SI-10
- SI-15
- SI-19
prerequisites:
- PT-3
severity_boost:
CA-6: "Chain with CA-6 for comprehensive security coverage"
CM-12: "Chain with CM-12 for comprehensive security coverage"
PM-5: "Chain with PM-5 for comprehensive security coverage"
---
# PT-3(2) Automation
> **Enhancement of:** PT-3
## High-Level Description
**Family:** Personally Identifiable Information Processing and Transparency (PT)
**Framework:** NIST SP 800-53 Rev 5
Automated mechanisms augment tracking of the processing purposes.
## What to Check
- [ ] Verify PT-3(2) Automation is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for PT-3(2)
- [ ] Verify enhancement builds upon base control PT-3
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for PT-3(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 |
| ------------- | --------------------------------- | ----- |
| Manual Review | Documentation and interview-based | N/A |
## Remediation Guide
### Control Statement
Track processing purposes of personally identifiable information using [organization-defined].
### Implementation Guidance
Automated mechanisms augment tracking of the processing purposes.
## Risk Assessment
| Finding | Severity | Impact |
| ---------------------------------- | -------- | -------------------------------------------------------------------------- |
| PT-3(2) Automation not implemented | Medium | Personally Identifiable Information Processing and Transparency |
| PT-3(2) partially implemented | Low | Incomplete Personally Identifiable Information Processing and Transparency |
## CWE Categories
| CWE ID | Title |
| ------- | ---------------------------------------- |
| CWE-359 | Exposure of Private Personal Information |
## References
- [NIST SP 800-53 Rev 5 - PT-3(2)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=pt-3.2)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
## Checklist
- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (CA-6, CM-12, PM-5, PM-22, SC-16) reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!