Implement [organization-defined] for individuals to revoke consent to the processing of their personally identifiable information.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill PT-4(3)_revocation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of PT 4(3) Revocation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-pt-4-3-revocation)More formats (shields.io, HTML) on the badges page.
---
name: "PT-4(3)_revocation"
description: "Implement [organization-defined] for individuals to revoke consent to the processing of their personally identifiable information."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- pt-4-3
- pt
- enhancement
tech_stack:
- any
cwe_ids:
- CWE-359
chains_with:
- PT-2
prerequisites:
- PT-4
severity_boost:
PT-2: "Chain with PT-2 for comprehensive security coverage"
---
# PT-4(3) Revocation
> **Enhancement of:** PT-4
## High-Level Description
**Family:** Personally Identifiable Information Processing and Transparency (PT)
**Framework:** NIST SP 800-53 Rev 5
Revocation of consent enables individuals to exercise control over their initial consent decision when circumstances change. Organizations consider usability factors in enabling easy-to-use revocation capabilities.
## What to Check
- [ ] Verify PT-4(3) Revocation is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for PT-4(3)
- [ ] Verify enhancement builds upon base control PT-4
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for PT-4(3) 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
Implement [organization-defined] for individuals to revoke consent to the processing of their personally identifiable information.
### Implementation Guidance
Revocation of consent enables individuals to exercise control over their initial consent decision when circumstances change. Organizations consider usability factors in enabling easy-to-use revocation capabilities.
## Risk Assessment
| Finding | Severity | Impact |
| ---------------------------------- | -------- | -------------------------------------------------------------------------- |
| PT-4(3) Revocation not implemented | Medium | Personally Identifiable Information Processing and Transparency |
| PT-4(3) 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-4(3)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=pt-4.3)
- [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 (PT-2) 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!