Notify the user, upon successful logon, of the number of [organization-defined] during [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill ac-9-2-successful-and-unsuccessful --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ac 9 2 Successful And Unsuccessful?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ac-9-2-successful-and-unsuccessful)More formats (shields.io, HTML) on the badges page.
---
name: "AC-9(2)_successful-and-unsuccessful-logons"
description: "Notify the user, upon successful logon, of the number of [organization-defined] during [organization-defined]."
category: "authorization"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ac-9-2
- ac
- enhancement
tech_stack:
- aws
- azure
- gcp
- linux
- windows
cwe_ids:
- CWE-284
chains_with: []
prerequisites:
- AC-9
severity_boost: {}
---
# AC-9(2) Successful and Unsuccessful Logons
> **Enhancement of:** AC-9
## High-Level Description
**Family:** Access Control (AC)
**Framework:** NIST SP 800-53 Rev 5
Information about the number of successful and unsuccessful logon attempts within a specified time period allows the user to recognize if the number and type of logon attempts are consistent with the user’s actual logon attempts.
## What to Check
- [ ] Verify AC-9(2) Successful and Unsuccessful Logons is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for AC-9(2)
- [ ] Verify enhancement builds upon base control AC-9
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AC-9(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 | Test web application access controls | `hackbrowser` |
## Remediation Guide
### Control Statement
Notify the user, upon successful logon, of the number of [organization-defined] during [organization-defined].
### Implementation Guidance
Information about the number of successful and unsuccessful logon attempts within a specified time period allows the user to recognize if the number and type of logon attempts are consistent with the user’s actual logon attempts.
## Risk Assessment
| Finding | Severity | Impact |
| ---------------------------------------------------------- | -------- | ------------------------- |
| AC-9(2) Successful and Unsuccessful Logons not implemented | High | Access Control |
| AC-9(2) partially implemented | Medium | Incomplete Access Control |
## CWE Categories
| CWE ID | Title |
| ------- | ----------------------- |
| CWE-284 | Improper Access Control |
## References
- [NIST SP 800-53 Rev 5 - AC-9(2)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ac-9.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 (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!