Enable AWS Security Hub Rule
Ensure compliance by enabling AWS Security Hub for an AWS Account according to Access Control benchmark.
| Rule | AWS Security Hub should be enabled for an AWS Account |
| Framework | NIST 800-171 Revision 2 |
| Severity | ✔ High |
Rule Description:
This rule ensures that AWS Security Hub is enabled for an AWS Account and checks for compliance with the NIST 800-171 Revision 2 security controls. The NIST 800-171 Revision 2 provides guidelines for protecting sensitive information in non-federal systems and organizations.
Troubleshooting Steps:
If AWS Security Hub is not enabled or is not compliant with the NIST 800-171 Revision 2 controls, follow the troubleshooting steps below:
- 1.
Verify AWS Security Hub Subscription:
- Go to the AWS Management Console.
- Open the Security Hub service.
- Check if Security Hub is enabled for the AWS Account. If not, enable it.
- 2.
Review Security Hub Check Status:
- In the Security Hub service, navigate to the "Standards" section.
- Look for the NIST 800-171 Revision 2 control checks.
- Check the status of each control check. If any control is not compliant, take necessary actions to remediate it.
- 3.
Review Security Hub Insights:
- Switch to the "Insights" tab in Security Hub.
- Look for any security findings related to non-compliant NIST 800-171 Revision 2 controls.
- Investigate each finding and remediate them as necessary.
Necessary Codes:
No specific code is required for this rule.
Remediation Steps:
To enable AWS Security Hub and ensure compliance with the NIST 800-171 Revision 2 controls, follow the steps below:
- 1.
Enable AWS Security Hub:
- Open the AWS Management Console.
- Navigate to the Security Hub service.
- Click on "Enable Security Hub".
- Select the AWS Account for which you want to enable Security Hub.
- Configure any additional settings if necessary.
- Click on "Enable Security Hub".
- 2.
Review Security Hub Configuration:
- In the Security Hub service, go to the "Standards" section.
- Look for the NIST 800-171 Revision 2 control checks.
- Review the status of each control. If any control is not compliant, proceed to the next step.
- 3.
Remediate Non-Compliant Controls:
- Identify the non-compliant controls listed in the Security Hub insights or control checks.
- Follow the remediation steps provided by AWS for each non-compliant control.
- Make the necessary configuration changes or apply additional security measures as required by the control.
- 4.
Validate Compliance:
- Review the Security Hub insights and control checks again.
- Ensure that all NIST 800-171 Revision 2 controls are now marked as compliant.
- Continue monitoring Security Hub and address any new findings or non-compliant controls promptly.
Additional Notes:
Enabling AWS Security Hub and ensuring compliance with NIST 800-171 Revision 2 controls helps organizations protect sensitive information and maintain a secure AWS environment. Regularly reviewing the Security Hub insights and status of control checks is essential to stay compliant with NIST guidelines and address any security risks promptly.