Bird
0
0

You have enabled Security Hub but no findings appear in the console. Which of the following is a likely cause?

medium📝 Debug Q7 of 15
AWS - Advanced Security
You have enabled Security Hub but no findings appear in the console. Which of the following is a likely cause?
ASecurity Hub only shows findings after 30 days of operation
BSecurity Hub requires manual import of findings from S3 buckets
CNo integrated AWS security services are enabled to send findings
DFindings are only visible if you use the AWS CLI, not the console
Step-by-Step Solution
Solution:
  1. Step 1: Understand Security Hub data sources

    Security Hub aggregates findings from integrated AWS services like GuardDuty, Inspector, and Macie.
  2. Step 2: Identify cause of no findings

    If these services are not enabled or integrated, Security Hub will have no findings to display.
  3. Step 3: Evaluate other options

    Security Hub requires manual import of findings from S3 buckets is incorrect; Security Hub does not require manual import from S3. Security Hub only shows findings after 30 days of operation is false; findings appear as soon as data is available. Findings are only visible if you use the AWS CLI, not the console is incorrect; findings are visible in both console and CLI.
  4. Final Answer:

    No integrated AWS security services are enabled to send findings -> Option C
  5. Quick Check:

    Enable services like GuardDuty to populate findings. [OK]
Quick Trick: Enable integrated services to generate findings. [OK]
Common Mistakes:
  • Assuming findings appear without enabling source services
  • Thinking findings require manual import

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes