- Newest
- Most votes
- Most comments
I believe yes, AWS Inspector 2 scans can be considered as authenticated internal scans to satisfy the PCI DSS 4.0 requirement 11.3.1.2, provided they meet certain criteria. PCI DSS 4.0 requirement 11.3.1.2 mandates authenticated internal vulnerability scans, which means the scans must use privileged credentials to access and assess internal systems.
To ensure AWS Inspector 2 scans meet this requirement, you should:
-
Use Privileged Credentials: Configure AWS Inspector 2 to use credentials that have sufficient privileges to access and scan internal systems.
-
Document Exceptions: If there are systems that cannot accept credentials, document these exceptions and account for them in your scanning process.
-
By configuring AWS Inspector 2 to perform authenticated scans with the necessary privileges, you can satisfy the PCI DSS 4.0 requirement 11.3.1.22.
Yes, AWS Inspector2 scans are considered as authenticated: Inspector scans are considered authenticated in accordance with Requirement 11.3.1.2. The scans occur from within the customer’s operating system.
References: [1]Payment Card Industry Data Security Standard (PCI DSS) v4.0 on AWS - page 32 https://d1.awsstatic.com/whitepapers/compliance/pci-dss-compliance-on-aws-v4-102023.pdf
[2]PCI DSS v4.0 on AWS Compliance Guide now available https://aws.amazon.com/blogs/security/pci-dss-v4-0-on-aws-compliance-guide-now-available/
Relevant content
asked 3 years ago
asked a year ago
asked 8 months ago
- AWS OFFICIALUpdated 8 months ago

Do you have any AWS documentation showing how to add credentials to AWS Inspector 2? I do not see any settings that allow this.