Inspector reports many vulnerabilities.
Prioritize remediation using severity and affected-asset information.
Which operational practice is most appropriate?
Aggregate Inspector findings in Security Hub and prioritize remediation by severity and asset context.
Detailed explanation
DNS TTL is not a vulnerability-scoring input.
DNS TTL is not a vulnerability-scoring input.
Centralized findings and asset context support consistent remediation priority.
Centralized findings and asset context support consistent remediation priority.
Archiving objects does not prioritize or remediate findings.
Archiving objects does not prioritize or remediate findings.
Deletion removes remediation evidence and audit context.
Deletion removes remediation evidence and audit context.
Check official documentation
Compare the following points with the official documentation.
Amazon Inspector findings integration with Security Hubの公式説明を確認する。
What to confirm
検出、集約、修復の各段階を説明できる。
Key points
- Inspector finding
- Security Hub
- Prioritization
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Risk-based queue
Severity alone is not enough; production exposure and asset importance affect priority.
Finding lifecycle
Aggregation preserves context while findings move through triage and remediation.