validation-rules

To validate AWS security findings, you map specific claim identifiers to deterministic, read-only AWS CLI commands. This standardizes evidence collection across IAM, compute, storage, and detection services for consistent verification.

Yes, you can verify external accessibility using read-only curl, nmap, or testssl.sh probe patterns. These external probes validate attacker-observable exposure across multiple AWS services without requiring write access.

Claim ID prefix lookup works by mapping a claim identifier prefix to a specific domain rule file, such as IAM or compute. Loading the correct file ensures the agent pipeline applies the right deterministic verification workflow for that check.

Standardizing false positive validation requires mapping each claim ID to concrete AWS CLI checks with deterministic read-only constraints. This defines exactly what confirmed and false positive mean for each security check across the pipeline.

Yes, evidence validation supports CloudTrail and IAM compliance through common baseline checks and domain-specific rule sets. Requesting verification for a claim ID like qa-05-cloudtrail loads the matching rules to run mapped AWS CLI evidence checks.