Use the following techniques to dispose of, destroy, or erase information following the retention period: [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill SI-12(3)_information-disposal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of SI 12(3) Information Disposal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-si-12-3-information-disposal)More formats (shields.io, HTML) on the badges page.
---
name: "SI-12(3)_information-disposal"
description: "Use the following techniques to dispose of, destroy, or erase information following the retention period: [organization-defined]."
category: "input-validation"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- si-12-3
- si
- enhancement
tech_stack:
- aws
- azure
- gcp
- linux
- windows
cwe_ids:
- CWE-20
chains_with: []
prerequisites:
- SI-12
severity_boost: {}
---
# SI-12(3) Information Disposal
> **Enhancement of:** SI-12
## High-Level Description
**Family:** System and Information Integrity (SI)
**Framework:** NIST SP 800-53 Rev 5
Organizations can minimize both security and privacy risks by disposing of information when it is no longer needed. The disposal or destruction of information applies to originals as well as copies and archived records, including system logs that may contain personally identifiable information.
## What to Check
- [ ] Verify SI-12(3) Information Disposal is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for SI-12(3)
- [ ] Verify enhancement builds upon base control SI-12
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SI-12(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 |
| --------------- | -------------------------- | ------------------------------ |
| cloud-audit-mcp | Check integrity monitoring | `cloud_audit_monitoring` |
| AWS CLI | Review GuardDuty/Inspector | `aws guardduty list-detectors` |
## Remediation Guide
### Control Statement
Use the following techniques to dispose of, destroy, or erase information following the retention period: [organization-defined].
### Implementation Guidance
Organizations can minimize both security and privacy risks by disposing of information when it is no longer needed. The disposal or destruction of information applies to originals as well as copies and archived records, including system logs that may contain personally identifiable information.
## Risk Assessment
| Finding | Severity | Impact |
| --------------------------------------------- | -------- | ------------------------------------------- |
| SI-12(3) Information Disposal not implemented | High | System and Information Integrity |
| SI-12(3) partially implemented | Medium | Incomplete System and Information Integrity |
## CWE Categories
| CWE ID | Title |
| ------ | ------------------------- |
| CWE-20 | Improper Input Validation |
## References
- [NIST SP 800-53 Rev 5 - SI-12(3)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=si-12.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 (none) 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!