Handle device identification and authentication based on attestation by [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill IA-3(4)_device-attestation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of IA 3(4) Device Attestation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ia-3-4-device-attestation)More formats (shields.io, HTML) on the badges page.
---
name: "IA-3(4)_device-attestation"
description: "Handle device identification and authentication based on attestation by [organization-defined]."
category: "authentication"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ia-3-4
- ia
- enhancement
tech_stack:
- aws
- azure
- active-directory
- linux
- windows
cwe_ids:
- CWE-287
chains_with:
- CM-2
- CM-3
- CM-6
prerequisites:
- IA-3
severity_boost:
CM-2: "Chain with CM-2 for comprehensive security coverage"
CM-3: "Chain with CM-3 for comprehensive security coverage"
CM-6: "Chain with CM-6 for comprehensive security coverage"
---
# IA-3(4) Device Attestation
> **Enhancement of:** IA-3
## High-Level Description
**Family:** Identification and Authentication (IA)
**Framework:** NIST SP 800-53 Rev 5
Device attestation refers to the identification and authentication of a device based on its configuration and known operating state. Device attestation can be determined via a cryptographic hash of the device. If device attestation is the means of identification and authentication, then it is important that patches and updates to the device are handled via a configuration management process such that the patches and updates are done securely and do not disrupt identification and authentication to other devices.
## What to Check
- [ ] Verify IA-3(4) Device Attestation is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for IA-3(4)
- [ ] Verify enhancement builds upon base control IA-3
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IA-3(4) 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 authentication settings | `cloud_audit_iam_policies` |
| hackbrowser | Test authentication mechanisms | `hackbrowser` |
## Remediation Guide
### Control Statement
Handle device identification and authentication based on attestation by [organization-defined].
### Implementation Guidance
Device attestation refers to the identification and authentication of a device based on its configuration and known operating state. Device attestation can be determined via a cryptographic hash of the device. If device attestation is the means of identification and authentication, then it is important that patches and updates to the device are handled via a configuration management process such that the patches and updates are done securely and do not disrupt identification and authentication to other devices.
## Risk Assessment
| Finding | Severity | Impact |
| ------------------------------------------ | -------- | -------------------------------------------- |
| IA-3(4) Device Attestation not implemented | High | Identification and Authentication |
| IA-3(4) partially implemented | Medium | Incomplete Identification and Authentication |
## CWE Categories
| CWE ID | Title |
| ------- | ----------------------- |
| CWE-287 | Improper Authentication |
## References
- [NIST SP 800-53 Rev 5 - IA-3(4)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ia-3.4)
- [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 (CM-2, CM-3, CM-6) 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!