Skip to content
Back to skills

Si 12 1 Limit Personally Identifiable

ASecurity

Limit personally identifiable information being processed in the information life cycle to the following elements of personally identifiable informati

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 3, 2026
securitygoawsgcpazuresecuritydocumentation

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill si-12-1-limit-personally-identifiable --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Si 12 1 Limit Personally Identifiable?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Si 12 1 Limit Personally Identifiable
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-si-12-1-limit-personally-identifiable/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-si-12-1-limit-personally-identifiable)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "SI-12(1)_limit-personally-identifiable-information-elements"
description: "Limit personally identifiable information being processed in the information life cycle to the following elements of personally identifiable informati"
category: "input-validation"
version: "5.2.0"
author: "cyberstrike-official"
tags:
  - nist
  - sp800-53
  - rev5
  - si-12-1
  - si
  - enhancement
tech_stack:
  - aws
  - azure
  - gcp
  - linux
  - windows
cwe_ids:
  - CWE-20
chains_with:
  - PM-25
prerequisites:
  - SI-12
severity_boost:
  PM-25: "Chain with PM-25 for comprehensive security coverage"
---

# SI-12(1) Limit Personally Identifiable Information Elements

> **Enhancement of:** SI-12

## High-Level Description

**Family:** System and Information Integrity (SI)
**Framework:** NIST SP 800-53 Rev 5

Limiting the use of personally identifiable information throughout the information life cycle when the information is not needed for operational purposes helps to reduce the level of privacy risk created by a system. The information life cycle includes information creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposition. Risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to determining which elements of personally identifiable information may create risk.

## What to Check

- [ ] Verify SI-12(1) Limit Personally Identifiable Information Elements is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for SI-12(1)
- [ ] 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(1) 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

Limit personally identifiable information being processed in the information life cycle to the following elements of personally identifiable information: [organization-defined].

### Implementation Guidance

Limiting the use of personally identifiable information throughout the information life cycle when the information is not needed for operational purposes helps to reduce the level of privacy risk created by a system. The information life cycle includes information creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposition. Risk assessments as well as applicable laws, regulations, and policies can provide useful inputs to determining which elements of personally identifiable information may create risk.

## Risk Assessment

| Finding                                                                     | Severity | Impact                                      |
| --------------------------------------------------------------------------- | -------- | ------------------------------------------- |
| SI-12(1) Limit Personally Identifiable Information Elements not implemented | High     | System and Information Integrity            |
| SI-12(1) 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(1)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=si-12.1)
- [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 (PM-25) reviewed

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.