1 Answer
- Newest
- Most votes
- Most comments
3
May worth to considering on below:
- Understand the STIG Compliance Levels: o The "low," "medium," and "high" compliance levels correspond to different categories of vulnerabilities. High compliance (Category I) addresses the most severe risks, while low compliance (Category III) focuses on less critical vulnerabilities.
- Review Logs for Insights: o Image Builder logs can provide details on which STIG settings are applied or skipped. Reviewing these logs can help identify the specific settings causing issues.
- Create Custom Components: o If the managed components are too restrictive, consider creating custom components to apply only the necessary STIG settings. This allows you to tailor the hardening process to your application's requirements.
- Test Incrementally: o Start with the "low" compliance level and test your application thoroughly. Gradually move to "medium" and "high" compliance levels, addressing issues as they arise.
- Use AWS Systems Manager: o AWS Systems Manager provides the AWSEC2-ConfigureSTIG command document, which allows you to apply STIG settings to instances. This document supports scoping down by selecting specific compliance categories.
https://docs.aws.amazon.com/imagebuilder/latest/userguide/ib-stig.html
Relevant content
- asked 2 months ago
- asked 2 years ago
- asked 2 months ago
- AWS OFFICIALUpdated 10 months ago