Study Guides/AWS Cybersecurity Notes/AWS Security Hub - Revision history

Mflavell: /* AWS Security Hub */

2026-05-25T23:21:30Z

AWS Security Hub

← Older revision		Revision as of 23:21, 25 May 2026
Line 114:		Line 114:

	:You must select an attribute to group by.		:You must select an attribute to group by.


			== Findings ==

			Findings are security issues helighted by AWS or Third party solutions.


			== Automated remediation ==

			Eventbridge and Security Hub can automatically trigger the following:

			:: AWS Lambda Function

			:: EC2 run command via Systems Manager

			:: AWS Step Functions State machine

			:: Sending an SNS notification

			:: Placing a message in SQS

			:: Sending findings to a third party system such as SIEM

Mflavell: /* Standards / Contoles and Checks */

2026-05-25T20:23:29Z

Standards / Contoles and Checks

@@ Line 80: / Line 80: @@
 Processing payment infomration
-:: Select PCI-DSS
+:: Select PCI-DSS (45 controls)
 Concerned about the CIA triad
-:: Select NIST 800-53
+:: Select NIST 800-53 (216 controls)

Mflavell: /* Standards / Contoles and Checks */

2026-05-25T20:14:46Z

Standards / Contoles and Checks

← Older revision		Revision as of 20:14, 25 May 2026
Line 75:		Line 75:
	::* NIST 800-53		::* NIST 800-53

	::* ~~PCIDSS~~		::* PCI-DSS


			Processing payment infomration

			:: Select PCI-DSS


			Concerned about the CIA triad

			:: Select NIST 800-53

Mflavell: /* AWS Security Hub */

2026-05-25T20:13:01Z

AWS Security Hub

← Older revision		Revision as of 20:13, 25 May 2026
Line 61:		Line 61:

	:: This data refresheshes security hub in alomost realtime		:: This data refresheshes security hub in alomost realtime


			== Standards / Contoles and Checks ==

			When enabling you are asked to select a security standard.

			Some of these are:

			::* AWS securirty bes practices

			::* CIS AWS Foundations benchmarks

			::* NIST 800-53

			::* PCIDSS

Mflavell: /* AWS Security Hub */

2026-05-25T19:51:35Z

AWS Security Hub

← Older revision		Revision as of 19:51, 25 May 2026
Line 51:		Line 51:

	HUB = '''H'''igh level		HUB = '''H'''igh level


			== Hub depends on config ==


			To enable AWS hub you must first have AWS Config enabled.

			:: Baseloine infomration for hub comes from AWS Config

			:: This data refresheshes security hub in alomost realtime

Mflavell: /* Compliance use case */

2026-05-25T19:48:23Z

Compliance use case

← Older revision		Revision as of 19:48, 25 May 2026
Line 50:		Line 50:


	HUB = '''H''''igh level		HUB = '''H'''igh level

Mflavell at 19:48, 25 May 2026

2026-05-25T19:48:04Z

← Older revision		Revision as of 19:48, 25 May 2026
Line 16:		Line 16:

	::Firewall Manager		::Firewall Manager


			Third party tools:

			:: AWS Security hub can be intergrated to work with many 3rd party applications.


			Think of security hub as a central point for a comprehehsive picture of security


			By default security hub is a regional service.

			:: Member and master accounts can be setup.

			::: Securty hub administrator is the core account

			::: Security hub member are the leaf accounts


			== Compliance use case ==

			Security hub can be used for automated compiance checks.


			Out of the box Security Hub performes 43 fully automated checks.

			:: They checks are based on the CIS foundations framework.


			Security hub looks at configutation and use at the account level.

			AWS config: looks at the resource level.


			HUB = '''H''''igh level

Mflavell: Created page with " = AWS Security Hub = This consolidates the security findings compliance and alerts. This includes: ::AWS IAM ::Macie ::Guard Duty ::Inspector ::Firewall Manager"

2026-05-25T01:46:31Z

Created page with " = AWS Security Hub = This consolidates the security findings compliance and alerts. This includes: ::AWS IAM ::Macie ::Guard Duty ::Inspector ::Firewall Manager"

New page

= AWS Security Hub =

This consolidates the security findings compliance and alerts.

This includes:

::AWS IAM

::Macie

::Guard Duty

::Inspector

::Firewall Manager