<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://cramsession.net/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mflavell</id>
	<title>Cramsession - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://cramsession.net/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mflavell"/>
	<link rel="alternate" type="text/html" href="https://cramsession.net/index.php/Special:Contributions/Mflavell"/>
	<updated>2026-05-27T02:12:11Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.1</generator>
	<entry>
		<id>https://cramsession.net/index.php?title=Copying_files_to_AWS_s3_from_Ubuntu&amp;diff=1646</id>
		<title>Copying files to AWS s3 from Ubuntu</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Copying_files_to_AWS_s3_from_Ubuntu&amp;diff=1646"/>
		<updated>2026-05-26T00:48:14Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Tech Notes]] &amp;gt; [[AWS]] &amp;gt; Copying files to AWS s3 from Ubuntu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= First, AWS tools =&lt;br /&gt;
&lt;br /&gt;
Make sure you have AWS tools installed before doing this.&lt;br /&gt;
&lt;br /&gt;
[[Installing AWS CLI]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Generare an key =&lt;br /&gt;
&lt;br /&gt;
* Login to the AWS IAM console.&lt;br /&gt;
&lt;br /&gt;
:* Select the the user for the app key&lt;br /&gt;
&lt;br /&gt;
:* Select &#039;&#039;Access keys&#039;&lt;br /&gt;
&lt;br /&gt;
:* Select &#039;&#039;Create Access key&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* In ubuntu run&lt;br /&gt;
&lt;br /&gt;
 aws configure&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Copy Commands =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy a single file ==&lt;br /&gt;
&lt;br /&gt;
 aws s3 cp display_server.ova s3://&#039;&#039;&#039;s3-bucket-name&#039;&#039;&#039;/&#039;&#039;&#039;path&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy a folder ==&lt;br /&gt;
&lt;br /&gt;
aws s3 sync . s3://YOURBUCKET/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Recursive copy of an extension ==&lt;br /&gt;
&lt;br /&gt;
 aws s3 cp . s3:/&#039;&#039;&#039;s3-bucket-name&#039;&#039;&#039;/ --recursive --exclude &amp;quot;*&amp;quot; --include &amp;quot;*.ova&amp;quot;&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1645</id>
		<title>Study Guides/AWS Cybersecurity Notes/Logging and Monitoring</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1645"/>
		<updated>2026-05-26T00:38:59Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Enabling S3 access logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Logging and Monitoring =&lt;br /&gt;
&lt;br /&gt;
The use of Cloud Watch is a important consideration - This can capture logs from AWS services and metrics to enable automation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Logging is of vital importance in diagnosis of security and performance issues in AWS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is possible to capture all logs in an S3 bucket, however this comes with a condition:&lt;br /&gt;
&lt;br /&gt;
:The access logs for the logging S3 bucket cannot be stored inside itself.&lt;br /&gt;
&lt;br /&gt;
:You will therefore need a seperate bucket for storing your S3 logging access logs.&lt;br /&gt;
&lt;br /&gt;
:: Access logging for the S3 logging bucket is highly recommended - an attacker may target logging to inject bad data or delete records.&lt;br /&gt;
&lt;br /&gt;
:Best practice is to create a access policy to ensure only the security team can read data from these buckets.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 [Main Logging bucket]&lt;br /&gt;
           |&lt;br /&gt;
          \|/&lt;br /&gt;
 writes access logs to&lt;br /&gt;
           |&lt;br /&gt;
          \|/&lt;br /&gt;
   [S3 logging bucket]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Delays in S3 logging ===&lt;br /&gt;
&lt;br /&gt;
Data is pushed to the S3 logging bucket on a &amp;quot;best effort&amp;quot; process.&lt;br /&gt;
&lt;br /&gt;
:: It can take a few hours to deliver s3 logs.&lt;br /&gt;
&lt;br /&gt;
:: S3 Logs will not be in realtime.&lt;br /&gt;
&lt;br /&gt;
::: AWS has a massive shared disk system - this is the reason behind the delay.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Enabling S3 access logs ==&lt;br /&gt;
&lt;br /&gt;
This assumes you already have a bucket you want to log.&lt;br /&gt;
&lt;br /&gt;
* Create a bucket to log data to.&lt;br /&gt;
&lt;br /&gt;
Crearte a JSON file to define where to place logs:&lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   &amp;quot;LoggingEnabled&amp;quot;: {&lt;br /&gt;
       &amp;quot;TargetBucket&amp;quot;: &amp;quot;logging bucket&amp;quot;,&lt;br /&gt;
       &amp;quot;TargetPrefix&amp;quot;: &amp;quot;S3Logs/&amp;quot;&lt;br /&gt;
   }&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Push the json file:&lt;br /&gt;
&lt;br /&gt;
 aws s3api put-bucket-logging --bucket &#039;&#039;s3_bucket_to_log&#039;&#039; --bucket-logging-status file://s3logs.json&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1644</id>
		<title>Study Guides/AWS Cybersecurity Notes/Logging and Monitoring</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1644"/>
		<updated>2026-05-26T00:23:30Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Logging and Monitoring */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Logging and Monitoring =&lt;br /&gt;
&lt;br /&gt;
The use of Cloud Watch is a important consideration - This can capture logs from AWS services and metrics to enable automation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Logging is of vital importance in diagnosis of security and performance issues in AWS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is possible to capture all logs in an S3 bucket, however this comes with a condition:&lt;br /&gt;
&lt;br /&gt;
:The access logs for the logging S3 bucket cannot be stored inside itself.&lt;br /&gt;
&lt;br /&gt;
:You will therefore need a seperate bucket for storing your S3 logging access logs.&lt;br /&gt;
&lt;br /&gt;
:: Access logging for the S3 logging bucket is highly recommended - an attacker may target logging to inject bad data or delete records.&lt;br /&gt;
&lt;br /&gt;
:Best practice is to create a access policy to ensure only the security team can read data from these buckets.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 [Main Logging bucket]&lt;br /&gt;
           |&lt;br /&gt;
          \|/&lt;br /&gt;
 writes access logs to&lt;br /&gt;
           |&lt;br /&gt;
          \|/&lt;br /&gt;
   [S3 logging bucket]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Delays in S3 logging ===&lt;br /&gt;
&lt;br /&gt;
Data is pushed to the S3 logging bucket on a &amp;quot;best effort&amp;quot; process.&lt;br /&gt;
&lt;br /&gt;
:: It can take a few hours to deliver s3 logs.&lt;br /&gt;
&lt;br /&gt;
:: S3 Logs will not be in realtime.&lt;br /&gt;
&lt;br /&gt;
::: AWS has a massive shared disk system - this is the reason behind the delay.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Enabling S3 access logs ==&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1643</id>
		<title>Study Guides/AWS Cybersecurity Notes/Logging and Monitoring</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1643"/>
		<updated>2026-05-26T00:19:49Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Logging and Monitoring */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Logging and Monitoring =&lt;br /&gt;
&lt;br /&gt;
The use of Cloud Watch is a important consideration - This can capture logs from AWS services and metrics to enable automation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Logging is of vital importance in diagnosis of security and performance issues in AWS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is possible to capture all logs in an S3 bucket, however this comes with a condition:&lt;br /&gt;
&lt;br /&gt;
:The access logs for the logging S3 bucket cannot be stored inside itself.&lt;br /&gt;
&lt;br /&gt;
:You will therefore need a seperate bucket for storing your S3 logging access logs.&lt;br /&gt;
&lt;br /&gt;
:: Access logging for the S3 logging bucket is highly recommended - an attacker may target logging to inject bad data or delete records.&lt;br /&gt;
&lt;br /&gt;
:Best practice is to create a access policy to ensure only the security team can read data from these buckets.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 [Main Logging bucket]&lt;br /&gt;
           |&lt;br /&gt;
          \|/&lt;br /&gt;
 writes access logs to&lt;br /&gt;
           |&lt;br /&gt;
          \|/&lt;br /&gt;
   [S3 logging bucket]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1642</id>
		<title>Study Guides/AWS Cybersecurity Notes/Logging and Monitoring</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Logging_and_Monitoring&amp;diff=1642"/>
		<updated>2026-05-26T00:19:11Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Created page with &amp;quot;= Logging and Monitoring =  The use of Cloud Watch is a important consideration - This can capture logs from AWS services and metrics to enable automation.   Logging is of vital importance in diagnosis of security and performance issues in AWS.   It is possible to capture all logs in an S3 bucket, however this comes with a condition:  :The access logs for the logging S3 bucket cannot be stored inside itself.  :You will therefore need a seperate bucket for storing your S3...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Logging and Monitoring =&lt;br /&gt;
&lt;br /&gt;
The use of Cloud Watch is a important consideration - This can capture logs from AWS services and metrics to enable automation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Logging is of vital importance in diagnosis of security and performance issues in AWS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is possible to capture all logs in an S3 bucket, however this comes with a condition:&lt;br /&gt;
&lt;br /&gt;
:The access logs for the logging S3 bucket cannot be stored inside itself.&lt;br /&gt;
&lt;br /&gt;
:You will therefore need a seperate bucket for storing your S3 logging access logs.&lt;br /&gt;
&lt;br /&gt;
:: Access logging for the S3 logging bucket is highly recommended - an attacker may target logging to inject bad data or delete records.&lt;br /&gt;
&lt;br /&gt;
:Best practice is to create a access policy to ensure only the security team can read data from these buckets.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 [Main Logging bucket]&lt;br /&gt;
           |&lt;br /&gt;
 writes access logs to&lt;br /&gt;
           |&lt;br /&gt;
   [S3 logging bucket]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1641</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1641"/>
		<updated>2026-05-26T00:07:59Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Config|AWS Config]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/Security Hub &amp;amp; Guard Duty|Security Hub and Guard Duty]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Security Hub|AWS Security Hub]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/Logging and Monitoring|Logging and Monitoring]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1640</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1640"/>
		<updated>2026-05-25T23:21:30Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* AWS Security Hub */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;igh level&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hub depends on config ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To enable AWS hub you must first have AWS Config enabled.&lt;br /&gt;
&lt;br /&gt;
:: Baseloine infomration for hub comes from AWS Config&lt;br /&gt;
&lt;br /&gt;
:: This data refresheshes security hub in alomost realtime&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Standards / Contoles and Checks ==&lt;br /&gt;
&lt;br /&gt;
When enabling you are asked to select a security standard.&lt;br /&gt;
&lt;br /&gt;
Some of these are:&lt;br /&gt;
&lt;br /&gt;
::* AWS securirty bes practices&lt;br /&gt;
&lt;br /&gt;
::* CIS AWS Foundations benchmarks&lt;br /&gt;
&lt;br /&gt;
::* NIST 800-53&lt;br /&gt;
&lt;br /&gt;
::* PCI-DSS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Processing payment infomration&lt;br /&gt;
&lt;br /&gt;
:: Select PCI-DSS (45 controls)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Concerned about the CIA triad&lt;br /&gt;
&lt;br /&gt;
:: Select NIST 800-53 (216 controls)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once a standard is enabled security checks will be run.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config is used to run the security checks.&lt;br /&gt;
&lt;br /&gt;
:: Checks can be done on a scedule.&lt;br /&gt;
&lt;br /&gt;
:: Checks can be done whenver a change is detected.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub uses the findings to generte a score.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security hub insights ==&lt;br /&gt;
&lt;br /&gt;
Managed insights:&lt;br /&gt;
&lt;br /&gt;
:These only work if the product is integrated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Custom insights:&lt;br /&gt;
&lt;br /&gt;
:Can be created with Security HUB API, AWS CLI or PowerShell&lt;br /&gt;
&lt;br /&gt;
:You must select an attribute to group by.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Findings ==&lt;br /&gt;
&lt;br /&gt;
Findings are security issues helighted by AWS or Third party solutions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Automated remediation ==&lt;br /&gt;
&lt;br /&gt;
Eventbridge and Security Hub can automatically trigger the following:&lt;br /&gt;
&lt;br /&gt;
:: AWS Lambda Function&lt;br /&gt;
&lt;br /&gt;
:: EC2 run command via Systems Manager&lt;br /&gt;
&lt;br /&gt;
:: AWS Step Functions State machine&lt;br /&gt;
&lt;br /&gt;
:: Sending an SNS notification&lt;br /&gt;
&lt;br /&gt;
:: Placing a message in SQS&lt;br /&gt;
&lt;br /&gt;
:: Sending findings to a third party system such as SIEM&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1639</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1639"/>
		<updated>2026-05-25T20:23:29Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Standards / Contoles and Checks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;igh level&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hub depends on config ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To enable AWS hub you must first have AWS Config enabled.&lt;br /&gt;
&lt;br /&gt;
:: Baseloine infomration for hub comes from AWS Config&lt;br /&gt;
&lt;br /&gt;
:: This data refresheshes security hub in alomost realtime&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Standards / Contoles and Checks ==&lt;br /&gt;
&lt;br /&gt;
When enabling you are asked to select a security standard.&lt;br /&gt;
&lt;br /&gt;
Some of these are:&lt;br /&gt;
&lt;br /&gt;
::* AWS securirty bes practices&lt;br /&gt;
&lt;br /&gt;
::* CIS AWS Foundations benchmarks&lt;br /&gt;
&lt;br /&gt;
::* NIST 800-53&lt;br /&gt;
&lt;br /&gt;
::* PCI-DSS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Processing payment infomration&lt;br /&gt;
&lt;br /&gt;
:: Select PCI-DSS (45 controls)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Concerned about the CIA triad&lt;br /&gt;
&lt;br /&gt;
:: Select NIST 800-53 (216 controls)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once a standard is enabled security checks will be run.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config is used to run the security checks.&lt;br /&gt;
&lt;br /&gt;
:: Checks can be done on a scedule.&lt;br /&gt;
&lt;br /&gt;
:: Checks can be done whenver a change is detected.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub uses the findings to generte a score.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security hub insights ==&lt;br /&gt;
&lt;br /&gt;
Managed insights:&lt;br /&gt;
&lt;br /&gt;
:These only work if the product is integrated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Custom insights:&lt;br /&gt;
&lt;br /&gt;
:Can be created with Security HUB API, AWS CLI or PowerShell&lt;br /&gt;
&lt;br /&gt;
:You must select an attribute to group by.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1638</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1638"/>
		<updated>2026-05-25T20:14:46Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Standards / Contoles and Checks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;igh level&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hub depends on config ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To enable AWS hub you must first have AWS Config enabled.&lt;br /&gt;
&lt;br /&gt;
:: Baseloine infomration for hub comes from AWS Config&lt;br /&gt;
&lt;br /&gt;
:: This data refresheshes security hub in alomost realtime&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Standards / Contoles and Checks ==&lt;br /&gt;
&lt;br /&gt;
When enabling you are asked to select a security standard.&lt;br /&gt;
&lt;br /&gt;
Some of these are:&lt;br /&gt;
&lt;br /&gt;
::* AWS securirty bes practices&lt;br /&gt;
&lt;br /&gt;
::* CIS AWS Foundations benchmarks&lt;br /&gt;
&lt;br /&gt;
::* NIST 800-53&lt;br /&gt;
&lt;br /&gt;
::* PCI-DSS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Processing payment infomration&lt;br /&gt;
&lt;br /&gt;
:: Select PCI-DSS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Concerned about the CIA triad&lt;br /&gt;
&lt;br /&gt;
:: Select NIST 800-53&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1637</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1637"/>
		<updated>2026-05-25T20:13:01Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* AWS Security Hub */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;igh level&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hub depends on config ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To enable AWS hub you must first have AWS Config enabled.&lt;br /&gt;
&lt;br /&gt;
:: Baseloine infomration for hub comes from AWS Config&lt;br /&gt;
&lt;br /&gt;
:: This data refresheshes security hub in alomost realtime&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Standards / Contoles and Checks ==&lt;br /&gt;
&lt;br /&gt;
When enabling you are asked to select a security standard.&lt;br /&gt;
&lt;br /&gt;
Some of these are:&lt;br /&gt;
&lt;br /&gt;
::* AWS securirty bes practices&lt;br /&gt;
&lt;br /&gt;
::* CIS AWS Foundations benchmarks&lt;br /&gt;
&lt;br /&gt;
::* NIST 800-53&lt;br /&gt;
&lt;br /&gt;
::* PCIDSS&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1636</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1636"/>
		<updated>2026-05-25T19:51:35Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* AWS Security Hub */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;igh level&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hub depends on config ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To enable AWS hub you must first have AWS Config enabled.&lt;br /&gt;
&lt;br /&gt;
:: Baseloine infomration for hub comes from AWS Config&lt;br /&gt;
&lt;br /&gt;
:: This data refresheshes security hub in alomost realtime&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1635</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1635"/>
		<updated>2026-05-25T19:48:23Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Compliance use case */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;igh level&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1634</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1634"/>
		<updated>2026-05-25T19:48:04Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Third party tools:&lt;br /&gt;
&lt;br /&gt;
:: AWS Security hub can be intergrated to work with many 3rd party applications.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Think of security hub as a central point for a comprehehsive picture of security&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default security hub is a regional service.&lt;br /&gt;
&lt;br /&gt;
:: Member and master accounts can be setup.&lt;br /&gt;
&lt;br /&gt;
::: Securty hub administrator is the core account&lt;br /&gt;
&lt;br /&gt;
::: Security hub member are the leaf accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Compliance use case ==&lt;br /&gt;
&lt;br /&gt;
Security hub can be used for automated compiance checks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Out of the box Security Hub performes 43 fully automated checks.&lt;br /&gt;
&lt;br /&gt;
:: They checks are based on the CIS foundations framework.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Security hub looks at configutation and use at the account level.&lt;br /&gt;
&lt;br /&gt;
AWS config: looks at the resource level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HUB = &#039;&#039;&#039;H&#039;&#039;&#039;&#039;igh level&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1633</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Security Hub</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Security_Hub&amp;diff=1633"/>
		<updated>2026-05-25T01:46:31Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Created page with &amp;quot; = AWS Security Hub =  This consolidates the security findings compliance and alerts.   This includes:  ::AWS IAM  ::Macie  ::Guard Duty  ::Inspector  ::Firewall Manager&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= AWS Security Hub =&lt;br /&gt;
&lt;br /&gt;
This consolidates the security findings compliance and alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This includes:&lt;br /&gt;
&lt;br /&gt;
::AWS IAM&lt;br /&gt;
&lt;br /&gt;
::Macie&lt;br /&gt;
&lt;br /&gt;
::Guard Duty&lt;br /&gt;
&lt;br /&gt;
::Inspector&lt;br /&gt;
&lt;br /&gt;
::Firewall Manager&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1632</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1632"/>
		<updated>2026-05-25T01:44:24Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Config|AWS Config]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/Security Hub &amp;amp; Guard Duty|Security Hub and Guard Duty]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Security Hub|AWS Security Hub]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1631</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1631"/>
		<updated>2026-05-25T01:36:51Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Findings &amp;amp; Cloudwatch */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Is charged to your account /not free.&lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
:: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
:: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
:: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
:: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Macie vs GuardDuty ==&lt;br /&gt;
&lt;br /&gt;
:: Macie looks at information stored in S3:&lt;br /&gt;
&lt;br /&gt;
::: Tries to classifiy the data and assess it&#039;s risk&lt;br /&gt;
&lt;br /&gt;
::: Macie is also a fullly managed macine learning system.&lt;br /&gt;
&lt;br /&gt;
::: Macie allows proactive safeguards on sesnsative infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: GuardDury does not:&lt;br /&gt;
&lt;br /&gt;
::: Read the S3 bucket data&lt;br /&gt;
&lt;br /&gt;
::: Find data containing PII&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: Guard duty does:&lt;br /&gt;
&lt;br /&gt;
::: Aggrigrate cloud trail events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Macie - inforMation&lt;br /&gt;
&lt;br /&gt;
Guard duty - Trails &amp;amp; logs (guards follow trails)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Severity of items ==&lt;br /&gt;
&lt;br /&gt;
A numerical scale is used for guard duty:&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;High&#039;&#039; - 7.0 - 8.9&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;Medium&#039;&#039; - 4.0.- 6.9&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;Low&#039;&#039; - 1.0 - 3.9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These values can be used to trigger SNS alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Testing Guard Duty ==&lt;br /&gt;
&lt;br /&gt;
AWS has a guard duty repo with simulated malware.&lt;br /&gt;
&lt;br /&gt;
More information can be found here: at https://github.com/awslabs/amazon-guardduty-tester&lt;br /&gt;
&lt;br /&gt;
This is a GIT repo that contains cloudformation templates.&lt;br /&gt;
&lt;br /&gt;
After setup findings should appear in guard duty after 8 to 10 minutes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Findings &amp;amp; Cloudwatch ==&lt;br /&gt;
&lt;br /&gt;
Multiple simular events will be combined - this is to prevent too much noise.&lt;br /&gt;
&lt;br /&gt;
:: An inital alert is sent out, guard duty then waits for a backoff period before alerting again.&lt;br /&gt;
&lt;br /&gt;
:: By default this period is six hours.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Remediation ==&lt;br /&gt;
&lt;br /&gt;
Any automated remeidation is done using cloudwatch.&lt;br /&gt;
&lt;br /&gt;
For manual, Guard duity provides a remeidation guide.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1630</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1630"/>
		<updated>2026-05-25T00:37:33Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Is charged to your account /not free.&lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
:: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
:: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
:: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
:: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Macie vs GuardDuty ==&lt;br /&gt;
&lt;br /&gt;
:: Macie looks at information stored in S3:&lt;br /&gt;
&lt;br /&gt;
::: Tries to classifiy the data and assess it&#039;s risk&lt;br /&gt;
&lt;br /&gt;
::: Macie is also a fullly managed macine learning system.&lt;br /&gt;
&lt;br /&gt;
::: Macie allows proactive safeguards on sesnsative infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: GuardDury does not:&lt;br /&gt;
&lt;br /&gt;
::: Read the S3 bucket data&lt;br /&gt;
&lt;br /&gt;
::: Find data containing PII&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: Guard duty does:&lt;br /&gt;
&lt;br /&gt;
::: Aggrigrate cloud trail events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Macie - inforMation&lt;br /&gt;
&lt;br /&gt;
Guard duty - Trails &amp;amp; logs (guards follow trails)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Severity of items ==&lt;br /&gt;
&lt;br /&gt;
A numerical scale is used for guard duty:&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;High&#039;&#039; - 7.0 - 8.9&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;Medium&#039;&#039; - 4.0.- 6.9&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;Low&#039;&#039; - 1.0 - 3.9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These values can be used to trigger SNS alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Testing Guard Duty ==&lt;br /&gt;
&lt;br /&gt;
AWS has a guard duty repo with simulated malware.&lt;br /&gt;
&lt;br /&gt;
More information can be found here: at https://github.com/awslabs/amazon-guardduty-tester&lt;br /&gt;
&lt;br /&gt;
This is a GIT repo that contains cloudformation templates.&lt;br /&gt;
&lt;br /&gt;
After setup findings should appear in guard duty after 8 to 10 minutes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Findings &amp;amp; Cloudwatch ==&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1629</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1629"/>
		<updated>2026-05-23T23:53:54Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Is charged to your account /not free.&lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
:: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
:: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
:: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
:: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Macie vs GuardDuty ==&lt;br /&gt;
&lt;br /&gt;
:: Macie looks at information stored in S3:&lt;br /&gt;
&lt;br /&gt;
::: Tries to classifiy the data and assess it&#039;s risk&lt;br /&gt;
&lt;br /&gt;
::: Macie is also a fullly managed macine learning system.&lt;br /&gt;
&lt;br /&gt;
::: Macie allows proactive safeguards on sesnsative infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: GuardDury does not:&lt;br /&gt;
&lt;br /&gt;
::: Read the S3 bucket data&lt;br /&gt;
&lt;br /&gt;
::: Find data containing PII&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: Guard duty does:&lt;br /&gt;
&lt;br /&gt;
::: Aggrigrate cloud trail events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Macie - inforMation&lt;br /&gt;
&lt;br /&gt;
Guard duty - Trails &amp;amp; logs (guards follow trails)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Severity of items ==&lt;br /&gt;
&lt;br /&gt;
A numerical scale is used for guard duty:&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;High&#039;&#039; - 7.0 - 8.9&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;Medium&#039;&#039; - 4.0.- 6.9&lt;br /&gt;
&lt;br /&gt;
::*&#039;&#039;Low&#039;&#039; - 1.0 - 3.9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These values can be used to trigger SNS alerts.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1628</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1628"/>
		<updated>2026-05-23T23:49:17Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Is charged to your account /not free.&lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
:: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
:: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
:: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
:: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Macie vs GuardDuty ==&lt;br /&gt;
&lt;br /&gt;
:: Macie looks at information stored in S3:&lt;br /&gt;
&lt;br /&gt;
::: Tries to classifiy the data and assess it&#039;s risk&lt;br /&gt;
&lt;br /&gt;
::: Macie is also a fullly managed macine learning system.&lt;br /&gt;
&lt;br /&gt;
::: Macie allows proactive safeguards on sesnsative infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: GuardDury does not:&lt;br /&gt;
&lt;br /&gt;
::: Read the S3 bucket data&lt;br /&gt;
&lt;br /&gt;
::: Find data containing PII&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: Guard duty does:&lt;br /&gt;
&lt;br /&gt;
::: Aggrigrate cloud trail events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Macie - inforMation&lt;br /&gt;
&lt;br /&gt;
Guard duty - Trails &amp;amp; logs (guards follow trails)&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1627</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1627"/>
		<updated>2026-05-23T23:47:36Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Amazon Guard Duty */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
:: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
:: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
:: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
:: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Macie vs GuardDuty ==&lt;br /&gt;
&lt;br /&gt;
:: Macie looks at information stored in S3:&lt;br /&gt;
&lt;br /&gt;
::: Tries to classifiy the data and assess it&#039;s risk&lt;br /&gt;
&lt;br /&gt;
::: Macie is also a fullly managed macine learning system.&lt;br /&gt;
&lt;br /&gt;
::: Macie allows proactive safeguards on sesnsative infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: GuardDury does not:&lt;br /&gt;
&lt;br /&gt;
::: Read the S3 bucket data&lt;br /&gt;
&lt;br /&gt;
::: Find data containing PII&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: Guard duty does:&lt;br /&gt;
&lt;br /&gt;
::: Aggrigrate cloud trail events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Macie - inforMation&lt;br /&gt;
&lt;br /&gt;
Guard duty - Trails &amp;amp; logs (guards follow trails)&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1626</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1626"/>
		<updated>2026-05-23T22:20:21Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Amazon Guard Duty */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
*: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
*: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
*: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
*: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Macie vs GuardDuty ==&lt;br /&gt;
&lt;br /&gt;
:: Macie looks at information stored in S3:&lt;br /&gt;
&lt;br /&gt;
::: Tries to classifiy the data and assess it&#039;s risk&lt;br /&gt;
&lt;br /&gt;
::: Macie is also a fullly managed macine learning system.&lt;br /&gt;
&lt;br /&gt;
::: Macie allows proactive safeguards on sesnsative infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: GuardDury does not:&lt;br /&gt;
&lt;br /&gt;
::: Read the S3 bucket data&lt;br /&gt;
&lt;br /&gt;
::: Find data containing PII&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:: Guard duty does:&lt;br /&gt;
&lt;br /&gt;
::: Aggrigrate cloud trail events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Macie - inforMation&lt;br /&gt;
&lt;br /&gt;
Guard duty - Trails &amp;amp; logs (guards follow trails)&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1625</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1625"/>
		<updated>2026-05-23T22:07:09Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
*: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
*: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
*: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
*: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GuardDuty Alerts ==&lt;br /&gt;
&lt;br /&gt;
All detections are ranked: High, Medium or Low&lt;br /&gt;
&lt;br /&gt;
:: This lets you know what items to address first.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Findings are devliered to three places:&lt;br /&gt;
&lt;br /&gt;
:: Your secutiy hub.&lt;br /&gt;
&lt;br /&gt;
:: A designated s3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: CloudWarch Events or Eventbridge&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* For this setup you must have &#039;&#039;&#039;security hub&#039;&#039;&#039; up and running.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why use these:&lt;br /&gt;
&lt;br /&gt;
:: Security hub - lets you see everything in one place.&lt;br /&gt;
&lt;br /&gt;
:: Cloudwatch / Eventbridge can provide near realtime alerts using SNS.&lt;br /&gt;
&lt;br /&gt;
:: S3 Keeps an audutable log of alerts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Where does infomaton come from ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guard duty uses these sources:&lt;br /&gt;
&lt;br /&gt;
:: AWS security intelegence&lt;br /&gt;
&lt;br /&gt;
:: AWS Partners such as CrowdString and Proofpoint&lt;br /&gt;
&lt;br /&gt;
:: Customer provided infomration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What can be detected ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using this intelgence GuardDuty can detect:&lt;br /&gt;
&lt;br /&gt;
:: Hosts infected with known malware.&lt;br /&gt;
&lt;br /&gt;
:: Proxies or TOR gateways&lt;br /&gt;
&lt;br /&gt;
:: Crypto mining or wallets&lt;br /&gt;
&lt;br /&gt;
:: Hosting of malware or hacking tools&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1624</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1624"/>
		<updated>2026-05-22T01:21:48Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* VPC Flow logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
*: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
*: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
*: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
*: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guard Duty Data Sources ==&lt;br /&gt;
&lt;br /&gt;
Once enabling guard duty, it will use these data sources...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* VPC Flow logs&lt;br /&gt;
&lt;br /&gt;
:: Provide details about network communication&lt;br /&gt;
&lt;br /&gt;
:: VPC flow logs can be turned off - because of this Guard Duty uses its onwn flow log stream.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* CloudTrail Events&lt;br /&gt;
&lt;br /&gt;
:: Stores SDK / Command line use for future reference.&lt;br /&gt;
&lt;br /&gt;
:: Helps build a profile of your account to understand norms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* DNS logs&lt;br /&gt;
&lt;br /&gt;
:: Checks for queries of known and unknown instances.&lt;br /&gt;
&lt;br /&gt;
:: Can look at domains queries and compre them to threat intelligence.&lt;br /&gt;
&lt;br /&gt;
:: Can be done with or without route 53 enabled.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1623</id>
		<title>Study Guides/AWS Cybersecurity Notes/Security Hub &amp; Guard Duty</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/Security_Hub_%26_Guard_Duty&amp;diff=1623"/>
		<updated>2026-05-22T01:14:58Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Created page with &amp;quot; = Amazon Guard Duty =  This is a managed threat detection service.  :* Uses machine learning   :* Can process millions of events, captured by:  ::* CloudTrail  ::* DNS (Route 53)  ::* VPC Flow longs   This service learns what is normal in the account to find abnormal actions.  :* Can detect connections with unisal sources.  :* EG: data been exfiltrated to a remote FTP server   This is a &amp;#039;&amp;#039;always on&amp;#039;&amp;#039; service:  :* Issues can be found without incurring a performance hit....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Amazon Guard Duty =&lt;br /&gt;
&lt;br /&gt;
This is a managed threat detection service.&lt;br /&gt;
&lt;br /&gt;
:* Uses machine learning &lt;br /&gt;
&lt;br /&gt;
:* Can process millions of events, captured by:&lt;br /&gt;
&lt;br /&gt;
::* CloudTrail&lt;br /&gt;
&lt;br /&gt;
::* DNS (Route 53)&lt;br /&gt;
&lt;br /&gt;
::* VPC Flow longs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This service learns what is normal in the account to find abnormal actions.&lt;br /&gt;
&lt;br /&gt;
:* Can detect connections with unisal sources.&lt;br /&gt;
&lt;br /&gt;
:* EG: data been exfiltrated to a remote FTP server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is a &#039;&#039;always on&#039;&#039; service:&lt;br /&gt;
&lt;br /&gt;
:* Issues can be found without incurring a performance hit.&lt;br /&gt;
&lt;br /&gt;
:* No local agentds are requires - this is Security as a Service.&lt;br /&gt;
&lt;br /&gt;
:* No upfront costs with GuardDuty.&lt;br /&gt;
&lt;br /&gt;
:* Installs in &#039;&#039;One Click&#039;&#039; no configuration nightmares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additionally:&lt;br /&gt;
&lt;br /&gt;
*: Coverage is global.&lt;br /&gt;
&lt;br /&gt;
*: Can detect intel-based well known threats&lt;br /&gt;
&lt;br /&gt;
*: Can find behaviour based threats&lt;br /&gt;
&lt;br /&gt;
*: Can monitor security over different accounts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== VPC Flow logs ==&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1622</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1622"/>
		<updated>2026-05-22T01:02:34Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Config|AWS Config]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/Security Hub &amp;amp; Guard Duty|Security Hub and Guard Duty]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1621</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1621"/>
		<updated>2026-05-22T01:01:51Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Config|AWS Config]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Config|Security Hub and Guard Duty]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1620</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Config</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1620"/>
		<updated>2026-05-21T16:06:21Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= What is AWS Config =&lt;br /&gt;
&lt;br /&gt;
AWS Config - records configurations and configuration changes.&lt;br /&gt;
&lt;br /&gt;
This is separate from cloud trail that records user events.&lt;br /&gt;
&lt;br /&gt;
: How to visualize this&lt;br /&gt;
&lt;br /&gt;
:: Peope leave trails 🚶... (Cloud Trail)&lt;br /&gt;
&lt;br /&gt;
:: Computers have configuration&lt;br /&gt;
&lt;br /&gt;
::: Cloudtrail = Who did it?&lt;br /&gt;
&lt;br /&gt;
::: AWS Config = What did they do?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS config has a &#039;&#039;configuration recorder&#039;&#039; that lets you inventory in real time.&lt;br /&gt;
&lt;br /&gt;
:: Can be used in across multiple regions or accounts.&lt;br /&gt;
&lt;br /&gt;
:: Resources can be evaluated constantly or on a fixed schedule.&lt;br /&gt;
&lt;br /&gt;
:: Lambda or System manager can be used to automatically remediate any compliance problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config allows a system to be continuously compliant by maintaining records of the systems sin&lt;br /&gt;
&lt;br /&gt;
:: Any time a change is made on the system - the change is captured with who or what made the change.&lt;br /&gt;
&lt;br /&gt;
:: This enabled auditing and checking of compliance levels at any time, on demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Why use AWS config =&lt;br /&gt;
&lt;br /&gt;
It is hard to understand what resources you are using in AWS.&lt;br /&gt;
&lt;br /&gt;
: Think of the problems running a massive system.&lt;br /&gt;
&lt;br /&gt;
:: How can you ever keep up with the what / where?&lt;br /&gt;
&lt;br /&gt;
:: How do you know what is no longer required?&lt;br /&gt;
&lt;br /&gt;
:: How do you know developers and engineers are following security policy?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for risk reduction:&lt;br /&gt;
&lt;br /&gt;
: Checking server exposure to the internet&lt;br /&gt;
&lt;br /&gt;
: Volumes that may not be encrypted.&lt;br /&gt;
&lt;br /&gt;
: Servers than hardening.&lt;br /&gt;
&lt;br /&gt;
: Accurate records of changes are recorded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What can AWS config do =&lt;br /&gt;
&lt;br /&gt;
* Checks configurations &lt;br /&gt;
&lt;br /&gt;
* Can save a snapshot of the current configuration&lt;br /&gt;
&lt;br /&gt;
* Lets you pull historical configurations&lt;br /&gt;
&lt;br /&gt;
* Allows the viewing of relationships&lt;br /&gt;
&lt;br /&gt;
* Can find resources been used easily and quickly&lt;br /&gt;
&lt;br /&gt;
* Can help reduce troubleshooting times though the comparison with the last known good configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Does AWS config have associated charges =&lt;br /&gt;
&lt;br /&gt;
* Yes - recoding has two different prices for continuous and periodic recording.&lt;br /&gt;
&lt;br /&gt;
* Rule evaulations will also cost you.&lt;br /&gt;
&lt;br /&gt;
* How to avoid pricing:&lt;br /&gt;
&lt;br /&gt;
:* Exclude resources you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Filter out regions or systems you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Monitor your bill!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= How AWS Config works =&lt;br /&gt;
&lt;br /&gt;
When a service is started AWS config scans the account for supported resources or services.&lt;br /&gt;
&lt;br /&gt;
: A configuation item is created for each resource or service.&lt;br /&gt;
&lt;br /&gt;
: Each time a change takes place a new configuration item is created.&lt;br /&gt;
&lt;br /&gt;
:: This allows changes to be determined in the configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Items ==&lt;br /&gt;
&lt;br /&gt;
These are snapshots that are stored in JSON format.&lt;br /&gt;
&lt;br /&gt;
: They represent the configuration at a point in time.&lt;br /&gt;
&lt;br /&gt;
: Most resources are supported by AWS Config - but not all.&lt;br /&gt;
&lt;br /&gt;
: An updare to the CI is made every time something changes on a monitored resource.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inside a configuration item:&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Metadata&#039;&#039; - Information about the configuration item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Attributes&#039;&#039; - Resourde data of the configuraton item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Relationship&#039;&#039; - Holds related data:&lt;br /&gt;
&lt;br /&gt;
:: For example subnet infomation or VPC infomation.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Current configuration&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Confguration recorder ==&lt;br /&gt;
&lt;br /&gt;
The configuration recorder discoveres changes in resources, new or existing.&lt;br /&gt;
&lt;br /&gt;
: These changes are then fed into configration item.&lt;br /&gt;
&lt;br /&gt;
: A configuration recorder is a must to monitor configurations.&lt;br /&gt;
&lt;br /&gt;
: The configuration recorder is the eyes of the config system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The recorder can be setup severa ways:&lt;br /&gt;
&lt;br /&gt;
:* Command line interface &lt;br /&gt;
&lt;br /&gt;
:* IaC - Infrastrcture as code such as:&lt;br /&gt;
&lt;br /&gt;
::* CloudFormation&lt;br /&gt;
&lt;br /&gt;
::* Terraform&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default this will setup configuration items for all resources by defauly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration role ==&lt;br /&gt;
&lt;br /&gt;
This is an IAM role that provides read only access to record the configuration items.&lt;br /&gt;
&lt;br /&gt;
This role also needs write permissions to the S3 bucket where the snapshots will be stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration streams ==&lt;br /&gt;
&lt;br /&gt;
When a new configuration item is created it&#039;s added to a configuration stream.&lt;br /&gt;
&lt;br /&gt;
The configuration stream is the same as an SNS topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Basic Setup =&lt;br /&gt;
&lt;br /&gt;
This provides a overview, for the exact CLI commands consult the AWS guides.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Create an S3 bucket to store the configuration items&lt;br /&gt;
&lt;br /&gt;
* Create an SNS topic for the config service&lt;br /&gt;
&lt;br /&gt;
* Create the IAM role for the config service:&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
  &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
    { &lt;br /&gt;
      &amp;quot;Sid&amp;quot;: &amp;quot;AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
      &amp;quot;Principal&amp;quot;: { &lt;br /&gt;
        &amp;quot;Service&amp;quot;: &amp;quot;config.amazonaws.com&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      &amp;quot;Action&amp;quot;: &amp;quot;sts:AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Condition&amp;quot;: { &lt;br /&gt;
   &amp;quot;StringEquals&amp;quot;: { &lt;br /&gt;
     &amp;quot;AWS:SourceAccount&amp;quot;: &amp;quot;your account number&amp;quot; &lt;br /&gt;
   } &lt;br /&gt;
      } &lt;br /&gt;
   } &lt;br /&gt;
 ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Saving this will give you a role ARN - &#039;&#039;&#039;&#039;This will be needed to start the configuration recorder&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
lets break the JSON down for better understanding:&lt;br /&gt;
&lt;br /&gt;
:* You want to &#039;&#039;Assume a role&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To &#039;&#039;Allow&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* The &#039;&#039;Config service&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To access &#039;&#039;Your aws account&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;Policy&#039;&#039;&#039; now needs to be created for the role to use, lets use this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
     &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
     &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
      { &lt;br /&gt;
        &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3PutPolicy&amp;quot;,&amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::packt-config/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &amp;quot;s3:GetBucketAcl&amp;quot; ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:aws:s3::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigSNSPolicy&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;: &amp;quot;sns:Publish&amp;quot;, &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:&#039;&#039;&#039;SNS-ARN&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;DescribeResources&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
         &amp;quot;ec2:Describe*&amp;quot;&lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot; &lt;br /&gt;
      } &lt;br /&gt;
    ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Let&#039;s break the JSON down for understanding:&lt;br /&gt;
&lt;br /&gt;
:* It provides access to the bucket to write objects&lt;br /&gt;
&lt;br /&gt;
:* It provides assess to SNS for push data&lt;br /&gt;
&lt;br /&gt;
:* It allows allows the discerption of ec2 resources &lt;br /&gt;
&lt;br /&gt;
The entire process is captured:&lt;br /&gt;
&lt;br /&gt;
: Describe &amp;gt; Transmit (SNS) &amp;gt; Save (s3)&lt;br /&gt;
&lt;br /&gt;
With this done we can attach the policy to the role:&lt;br /&gt;
&lt;br /&gt;
This can be done in the AWS CLI with the following command:&lt;br /&gt;
&lt;br /&gt;
 aws iam attach-role-policy --role-name &#039;&#039;&#039;role name&#039;&#039;&#039; --policy-arn &#039;&#039;&#039;policy arn&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next and very importantly we need to determine what resources to capture.&lt;br /&gt;
&lt;br /&gt;
:* Keep in mind you will pay a nominal free for these / but this is AWS - resources add up $$$&lt;br /&gt;
&lt;br /&gt;
:* If you monitor too little you won&#039;t get the data you need to make decisions or protect the system.&lt;br /&gt;
&lt;br /&gt;
:* Decide what is right for your system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of the JSON file:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
           &amp;quot;allSupported&amp;quot;: false, &lt;br /&gt;
           &amp;quot;includeGlobalResourceTypes&amp;quot;: false, &lt;br /&gt;
           &amp;quot;resourceTypes&amp;quot;: [ &lt;br /&gt;
                   &amp;quot;AWS::EC2::SecurityGroup&amp;quot;, &lt;br /&gt;
                   &amp;quot;AWS::EC2::Volume&amp;quot; &lt;br /&gt;
           ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will monitor:&lt;br /&gt;
&lt;br /&gt;
::* EC2 security groups.&lt;br /&gt;
&lt;br /&gt;
::* EC2 Volue status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next create a delivery file:&lt;br /&gt;
&lt;br /&gt;
{ &lt;br /&gt;
           &amp;quot;name&amp;quot;: &amp;quot;default&amp;quot;, &lt;br /&gt;
           &amp;quot;s3BucketName&amp;quot;: &amp;quot;&#039;&#039;your-bucket&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;snsTopicARN&amp;quot;: &amp;quot;arn:aws:sns:&#039;&#039;your-sns&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;configSnapshotDeliveryProperties&amp;quot;: { &lt;br /&gt;
               &amp;quot;deliveryFrequency&amp;quot;: &amp;quot;Twelve_Hours&amp;quot; &lt;br /&gt;
           } &lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
::* Connects the S3 bucket&lt;br /&gt;
&lt;br /&gt;
::* Connects the SNS&lt;br /&gt;
&lt;br /&gt;
::* Defines the frequency&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, start the recorder&lt;br /&gt;
&lt;br /&gt;
 aws configservice start-configuration-recorder --configuration-recorder-name &#039;&#039;name&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::* It will take a few minutes for the data to be posted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AWS Config Rules =&lt;br /&gt;
&lt;br /&gt;
Rules enable you to automatically evaluate the configuration of monitored resources.&lt;br /&gt;
&lt;br /&gt;
A rule can be triggered in two ways:&lt;br /&gt;
&lt;br /&gt;
:* When a resource changes&lt;br /&gt;
&lt;br /&gt;
:* On a schedule&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These rules allow you to enfore a consistant approach to AWS resources.&lt;br /&gt;
&lt;br /&gt;
: This is independent of who deployed them or when they where deployed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rules can apply to ==&lt;br /&gt;
&lt;br /&gt;
:* A single or a set of resouce ID&#039;s&lt;br /&gt;
&lt;br /&gt;
:* Types of resources &lt;br /&gt;
&lt;br /&gt;
:* Resources with a specified tag&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rules help enforce compliance.&lt;br /&gt;
&lt;br /&gt;
: Labmba functions can also be used to add logic to the rules.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AWS Config Managed Rules ==&lt;br /&gt;
&lt;br /&gt;
These are preconfigured to ensure your systems comply to industry best practices.&lt;br /&gt;
&lt;br /&gt;
For custom rules their is no need for write an action - it is performed automatically.&lt;br /&gt;
&lt;br /&gt;
Over 150 managed rules exist today.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Custom Rules ==&lt;br /&gt;
&lt;br /&gt;
Custom rules can be created using two methods:&lt;br /&gt;
&lt;br /&gt;
:* AWS Lambda &lt;br /&gt;
&lt;br /&gt;
:* A Guard policy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rule Evaluation ==&lt;br /&gt;
&lt;br /&gt;
:* Proactive mode - Immimdate evaluation&lt;br /&gt;
&lt;br /&gt;
:* Detective mode - Evaulated against resources that are already depoyed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conformance packs ==&lt;br /&gt;
&lt;br /&gt;
:* These make it easy to implement best practices.&lt;br /&gt;
&lt;br /&gt;
:* Can be run in a region or over multiple regions via aggregator.&lt;br /&gt;
&lt;br /&gt;
:* Enables a one click setup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Configuration History =&lt;br /&gt;
&lt;br /&gt;
As you may expect, this lists all the changes made to a resource.&lt;br /&gt;
&lt;br /&gt;
:: This is done by comparing the configuration items saved in the S3 bucket.&lt;br /&gt;
&lt;br /&gt;
:: Use case: Determine the history of events that resulted in an incident.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Fixing no compliant resources =&lt;br /&gt;
&lt;br /&gt;
This is possible out of the box though the use of &#039;&#039;System Manager Automation Runbooks&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:: Contain predefined automated remediations.&lt;br /&gt;
&lt;br /&gt;
:: Custom remediations can also be created.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Using Multiple accounts =&lt;br /&gt;
&lt;br /&gt;
This is done using aggregator, the use cases are:&lt;br /&gt;
&lt;br /&gt;
:* Single account / Multi region&lt;br /&gt;
&lt;br /&gt;
:* Multi account / Multi region&lt;br /&gt;
&lt;br /&gt;
The aggregator makes finding trends in multiple regions or accounts easier by consolidating the data.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1619</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1619"/>
		<updated>2026-05-21T15:54:44Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Cramsession Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
=== Do no harm ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;👉Breaking these will get you a lifetime ban&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Help each other on our journey ===&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* If you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
:* Keep the site clean - Use the the correct naming format for pages:  /Study Guides/&#039;&#039;major topic&#039;&#039;/&#039;&#039;your guide name&#039;&#039;/&#039;&#039;sub topic&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::* Some of the older pages may not have this format - we are working on updating that.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== We are here... for all mankind ===&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Keep your author account in good standing ===&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1618</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1618"/>
		<updated>2026-05-21T15:53:53Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Help each other on our journey */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
=== Do no harm ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;👉Breaking these will get you a lifetime ban&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Help each other on our journey ===&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* If you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
:* Keep the site clean - Use the the correct naming format for pages:  /Study Guides/&#039;&#039;major topic&#039;&#039;/&#039;&#039;your guide name&#039;&#039;/&#039;&#039;sub topic&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::* Some of the older pages may not have this format - we are working on updating that.&lt;br /&gt;
&lt;br /&gt;
=== We are here... for all mankind ===&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Keep your author account in good standing ===&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1617</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1617"/>
		<updated>2026-05-21T15:50:33Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[Study Guides/AWS Cybersecurity Notes/AWS Config|AWS Config]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1616</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Config</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1616"/>
		<updated>2026-05-21T15:50:03Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Mflavell moved page AWS Config to Study Guides/AWS Cybersecurity Notes/AWS Config without leaving a redirect&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= What is AWS Config =&lt;br /&gt;
&lt;br /&gt;
AWS Config - records configurations and configuration changes.&lt;br /&gt;
&lt;br /&gt;
This is separate from cloud trail that records user events.&lt;br /&gt;
&lt;br /&gt;
: How to visualize this&lt;br /&gt;
&lt;br /&gt;
:: Peope leave trails 🚶... (Cloud Trail)&lt;br /&gt;
&lt;br /&gt;
:: Computers have configuration&lt;br /&gt;
&lt;br /&gt;
::: Cloudtrail = Who did it?&lt;br /&gt;
&lt;br /&gt;
::: AWS Config = What did they do?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS config has a &#039;&#039;configuration recorder&#039;&#039; that lets you inventory in real time.&lt;br /&gt;
&lt;br /&gt;
:: Can be used in across multiple regions or accounts.&lt;br /&gt;
&lt;br /&gt;
:: Resources can be evaluated constantly or on a fixed schedule.&lt;br /&gt;
&lt;br /&gt;
:: Lambda or System manager can be used to automatically remediate any compliance problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config allows a system to be continuously compliant by maintaining records of the systems sin&lt;br /&gt;
&lt;br /&gt;
:: Any time a change is made on the system - the change is captured with who or what made the change.&lt;br /&gt;
&lt;br /&gt;
:: This enabled auditing and checking of compliance levels at any time, on demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Why use AWS config =&lt;br /&gt;
&lt;br /&gt;
It is hard to understand what resources you are using in AWS.&lt;br /&gt;
&lt;br /&gt;
: Think of the problems running a massive system.&lt;br /&gt;
&lt;br /&gt;
:: How can you ever keep up with the what / where?&lt;br /&gt;
&lt;br /&gt;
:: How do you know what is no longer required?&lt;br /&gt;
&lt;br /&gt;
:: How do you know developers and engineers are following security policy?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for risk reduction:&lt;br /&gt;
&lt;br /&gt;
: Checking server exposure to the internet&lt;br /&gt;
&lt;br /&gt;
: Volumes that may not be encrypted.&lt;br /&gt;
&lt;br /&gt;
: Servers than hardening.&lt;br /&gt;
&lt;br /&gt;
: Accurate records of changes are recorded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What can AWS config do =&lt;br /&gt;
&lt;br /&gt;
* Checks configurations &lt;br /&gt;
&lt;br /&gt;
* Can save a snapshot of the current configuration&lt;br /&gt;
&lt;br /&gt;
* Lets you pull historical configurations&lt;br /&gt;
&lt;br /&gt;
* Allows the viewing of relationships&lt;br /&gt;
&lt;br /&gt;
* Can find resources been used easily and quickly&lt;br /&gt;
&lt;br /&gt;
* Can help reduce troubleshooting times though the comparison with the last known good configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Does AWS config have associated charges =&lt;br /&gt;
&lt;br /&gt;
* Yes - recoding has two different prices for continuous and periodic recording.&lt;br /&gt;
&lt;br /&gt;
* Rule evaulations will also cost you.&lt;br /&gt;
&lt;br /&gt;
* How to avoid pricing:&lt;br /&gt;
&lt;br /&gt;
:* Exclude resources you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Filter out regions or systems you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Monitor your bill!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= How AWS Config works =&lt;br /&gt;
&lt;br /&gt;
When a service is started AWS config scans the account for supported resources or services.&lt;br /&gt;
&lt;br /&gt;
: A configuation item is created for each resource or service.&lt;br /&gt;
&lt;br /&gt;
: Each time a change takes place a new configuration item is created.&lt;br /&gt;
&lt;br /&gt;
:: This allows changes to be determined in the configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Items ==&lt;br /&gt;
&lt;br /&gt;
These are snapshots that are stored in JSON format.&lt;br /&gt;
&lt;br /&gt;
: They represent the configuration at a point in time.&lt;br /&gt;
&lt;br /&gt;
: Most resources are supported by AWS Config - but not all.&lt;br /&gt;
&lt;br /&gt;
: An updare to the CI is made every time something changes on a monitored resource.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inside a configuration item:&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Metadata&#039;&#039; - Information about the configuration item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Attributes&#039;&#039; - Resourde data of the configuraton item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Relationship&#039;&#039; - Holds related data:&lt;br /&gt;
&lt;br /&gt;
:: For example subnet infomation or VPC infomation.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Current configuration&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Confguration recorder ==&lt;br /&gt;
&lt;br /&gt;
The configuration recorder discoveres changes in resources, new or existing.&lt;br /&gt;
&lt;br /&gt;
: These changes are then fed into configration item.&lt;br /&gt;
&lt;br /&gt;
: A configuration recorder is a must to monitor configurations.&lt;br /&gt;
&lt;br /&gt;
: The configuration recorder is the eyes of the config system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The recorder can be setup severa ways:&lt;br /&gt;
&lt;br /&gt;
:* Command line interface &lt;br /&gt;
&lt;br /&gt;
:* IaC - Infrastrcture as code such as:&lt;br /&gt;
&lt;br /&gt;
::* CloudFormation&lt;br /&gt;
&lt;br /&gt;
::* Terraform&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default this will setup configuration items for all resources by defauly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration role ==&lt;br /&gt;
&lt;br /&gt;
This is an IAM role that provides read only access to record the configuration items.&lt;br /&gt;
&lt;br /&gt;
This role also needs write permissions to the S3 bucket where the snapshots will be stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration streams ==&lt;br /&gt;
&lt;br /&gt;
When a new configuration item is created it&#039;s added to a configuration stream.&lt;br /&gt;
&lt;br /&gt;
The configuration stream is the same as an SNS topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Basic Setup =&lt;br /&gt;
&lt;br /&gt;
This provides a overview, for the exact CLI commands consult the AWS guides.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Create an S3 bucket to store the configuration items&lt;br /&gt;
&lt;br /&gt;
* Create an SNS topic for the config service&lt;br /&gt;
&lt;br /&gt;
* Create the IAM role for the config service:&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
  &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
    { &lt;br /&gt;
      &amp;quot;Sid&amp;quot;: &amp;quot;AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
      &amp;quot;Principal&amp;quot;: { &lt;br /&gt;
        &amp;quot;Service&amp;quot;: &amp;quot;config.amazonaws.com&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      &amp;quot;Action&amp;quot;: &amp;quot;sts:AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Condition&amp;quot;: { &lt;br /&gt;
   &amp;quot;StringEquals&amp;quot;: { &lt;br /&gt;
     &amp;quot;AWS:SourceAccount&amp;quot;: &amp;quot;your account number&amp;quot; &lt;br /&gt;
   } &lt;br /&gt;
      } &lt;br /&gt;
   } &lt;br /&gt;
 ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Saving this will give you a role ARN - &#039;&#039;&#039;&#039;This will be needed to start the configuration recorder&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
lets break the JSON down for better understanding:&lt;br /&gt;
&lt;br /&gt;
:* You want to &#039;&#039;Assume a role&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To &#039;&#039;Allow&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* The &#039;&#039;Config service&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To access &#039;&#039;Your aws account&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;Policy&#039;&#039;&#039; now needs to be created for the role to use, lets use this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
     &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
     &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
      { &lt;br /&gt;
        &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3PutPolicy&amp;quot;,&amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::packt-config/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &amp;quot;s3:GetBucketAcl&amp;quot; ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:aws:s3::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigSNSPolicy&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;: &amp;quot;sns:Publish&amp;quot;, &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:&#039;&#039;&#039;SNS-ARN&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;DescribeResources&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
         &amp;quot;ec2:Describe*&amp;quot;&lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot; &lt;br /&gt;
      } &lt;br /&gt;
    ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Let&#039;s break the JSON down for understanding:&lt;br /&gt;
&lt;br /&gt;
:* It provides access to the bucket to write objects&lt;br /&gt;
&lt;br /&gt;
:* It provides assess to SNS for push data&lt;br /&gt;
&lt;br /&gt;
:* It allows allows the discerption of ec2 resources &lt;br /&gt;
&lt;br /&gt;
The entire process is captured:&lt;br /&gt;
&lt;br /&gt;
: Describe &amp;gt; Transmit (SNS) &amp;gt; Save (s3)&lt;br /&gt;
&lt;br /&gt;
With this done we can attach the policy to the role:&lt;br /&gt;
&lt;br /&gt;
This can be done in the AWS CLI with the following command:&lt;br /&gt;
&lt;br /&gt;
 aws iam attach-role-policy --role-name &#039;&#039;&#039;role name&#039;&#039;&#039; --policy-arn &#039;&#039;&#039;policy arn&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next and very importantly we need to determine what resources to capture.&lt;br /&gt;
&lt;br /&gt;
:* Keep in mind you will pay a nominal free for these / but this is AWS - resources add up $$$&lt;br /&gt;
&lt;br /&gt;
:* If you monitor too little you won&#039;t get the data you need to make decisions or protect the system.&lt;br /&gt;
&lt;br /&gt;
:* Decide what is right for your system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of the JSON file:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
           &amp;quot;allSupported&amp;quot;: false, &lt;br /&gt;
           &amp;quot;includeGlobalResourceTypes&amp;quot;: false, &lt;br /&gt;
           &amp;quot;resourceTypes&amp;quot;: [ &lt;br /&gt;
                   &amp;quot;AWS::EC2::SecurityGroup&amp;quot;, &lt;br /&gt;
                   &amp;quot;AWS::EC2::Volume&amp;quot; &lt;br /&gt;
           ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will monitor:&lt;br /&gt;
&lt;br /&gt;
::* EC2 security groups.&lt;br /&gt;
&lt;br /&gt;
::* EC2 Volue status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next create a delivery file:&lt;br /&gt;
&lt;br /&gt;
{ &lt;br /&gt;
           &amp;quot;name&amp;quot;: &amp;quot;default&amp;quot;, &lt;br /&gt;
           &amp;quot;s3BucketName&amp;quot;: &amp;quot;&#039;&#039;your-bucket&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;snsTopicARN&amp;quot;: &amp;quot;arn:aws:sns:&#039;&#039;your-sns&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;configSnapshotDeliveryProperties&amp;quot;: { &lt;br /&gt;
               &amp;quot;deliveryFrequency&amp;quot;: &amp;quot;Twelve_Hours&amp;quot; &lt;br /&gt;
           } &lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
::* Connects the S3 bucket&lt;br /&gt;
&lt;br /&gt;
::* Connects the SNS&lt;br /&gt;
&lt;br /&gt;
::* Defines the frequency&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, start the recorder&lt;br /&gt;
&lt;br /&gt;
 aws configservice start-configuration-recorder --configuration-recorder-name &#039;&#039;name&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::* It will take a few minutes for the data to be posted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AWS Config Rules =&lt;br /&gt;
&lt;br /&gt;
Rules enable you to automatically evaluate the configuration of monitored resources.&lt;br /&gt;
&lt;br /&gt;
A rule can be triggered in two ways:&lt;br /&gt;
&lt;br /&gt;
:* When a resource changes&lt;br /&gt;
&lt;br /&gt;
:* On a schedule&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These rules allow you to enfore a consistant approach to AWS resources.&lt;br /&gt;
&lt;br /&gt;
: This is independent of who deployed them or when they where deployed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rules can apply to ==&lt;br /&gt;
&lt;br /&gt;
:* A single or a set of resouce ID&#039;s&lt;br /&gt;
&lt;br /&gt;
:* Types of resources &lt;br /&gt;
&lt;br /&gt;
:* Resources with a specified tag&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rules help enforce compliance.&lt;br /&gt;
&lt;br /&gt;
: Labmba functions can also be used to add logic to the rules.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AWS Config Managed Rules ==&lt;br /&gt;
&lt;br /&gt;
These are preconfigured to ensure your systems comply to industry best practices.&lt;br /&gt;
&lt;br /&gt;
For custom rules their is no need for write an action - it is performed automatically.&lt;br /&gt;
&lt;br /&gt;
Over 150 managed rules exist today.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Custom Rules ==&lt;br /&gt;
&lt;br /&gt;
Custom rules can be created using two methods:&lt;br /&gt;
&lt;br /&gt;
:* AWS Lambda &lt;br /&gt;
&lt;br /&gt;
:* A Guard policy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rule Evaluation ==&lt;br /&gt;
&lt;br /&gt;
:* Proactive mode - Immimdate evaluation&lt;br /&gt;
&lt;br /&gt;
:* Detective mode - Evaulated against resources that are already depoyed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conformance packs ==&lt;br /&gt;
&lt;br /&gt;
:* These make it easy to implement best practices.&lt;br /&gt;
&lt;br /&gt;
:* Can be run in a region or over multiple regions via aggregator.&lt;br /&gt;
&lt;br /&gt;
:* Enables a one click setup.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1615</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1615"/>
		<updated>2026-05-21T15:49:16Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Config]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides&amp;diff=1614</id>
		<title>Study Guides</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides&amp;diff=1614"/>
		<updated>2026-05-21T15:48:44Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=SCS-C02 Cybersecurity Specialist=&lt;br /&gt;
&lt;br /&gt;
📗[[Study Guides/AWS Cybersecurity Notes|AWS Cybersecurity Notes]]&lt;br /&gt;
&lt;br /&gt;
=Multiple Choice Guide=&lt;br /&gt;
&lt;br /&gt;
✅[https://www.dmu.edu/wp-content/uploads/MULTIPLE-CHOICE-TEST-TAKING-STRATEGIES.pdf Hacking Multiple Choice Questions]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides&amp;diff=1613</id>
		<title>Study Guides</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides&amp;diff=1613"/>
		<updated>2026-05-21T15:48:12Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=SCS-C02 Cybersecurity Specialist=&lt;br /&gt;
&lt;br /&gt;
📗[[Study Guides/AWS Cybersecurity Notes AWS Cybersecurity Notes]]&lt;br /&gt;
&lt;br /&gt;
=Multiple Choice Guide=&lt;br /&gt;
&lt;br /&gt;
✅[https://www.dmu.edu/wp-content/uploads/MULTIPLE-CHOICE-TEST-TAKING-STRATEGIES.pdf Hacking Multiple Choice Questions]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1612</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Config</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1612"/>
		<updated>2026-05-21T15:47:02Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= What is AWS Config =&lt;br /&gt;
&lt;br /&gt;
AWS Config - records configurations and configuration changes.&lt;br /&gt;
&lt;br /&gt;
This is separate from cloud trail that records user events.&lt;br /&gt;
&lt;br /&gt;
: How to visualize this&lt;br /&gt;
&lt;br /&gt;
:: Peope leave trails 🚶... (Cloud Trail)&lt;br /&gt;
&lt;br /&gt;
:: Computers have configuration&lt;br /&gt;
&lt;br /&gt;
::: Cloudtrail = Who did it?&lt;br /&gt;
&lt;br /&gt;
::: AWS Config = What did they do?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS config has a &#039;&#039;configuration recorder&#039;&#039; that lets you inventory in real time.&lt;br /&gt;
&lt;br /&gt;
:: Can be used in across multiple regions or accounts.&lt;br /&gt;
&lt;br /&gt;
:: Resources can be evaluated constantly or on a fixed schedule.&lt;br /&gt;
&lt;br /&gt;
:: Lambda or System manager can be used to automatically remediate any compliance problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config allows a system to be continuously compliant by maintaining records of the systems sin&lt;br /&gt;
&lt;br /&gt;
:: Any time a change is made on the system - the change is captured with who or what made the change.&lt;br /&gt;
&lt;br /&gt;
:: This enabled auditing and checking of compliance levels at any time, on demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Why use AWS config =&lt;br /&gt;
&lt;br /&gt;
It is hard to understand what resources you are using in AWS.&lt;br /&gt;
&lt;br /&gt;
: Think of the problems running a massive system.&lt;br /&gt;
&lt;br /&gt;
:: How can you ever keep up with the what / where?&lt;br /&gt;
&lt;br /&gt;
:: How do you know what is no longer required?&lt;br /&gt;
&lt;br /&gt;
:: How do you know developers and engineers are following security policy?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for risk reduction:&lt;br /&gt;
&lt;br /&gt;
: Checking server exposure to the internet&lt;br /&gt;
&lt;br /&gt;
: Volumes that may not be encrypted.&lt;br /&gt;
&lt;br /&gt;
: Servers than hardening.&lt;br /&gt;
&lt;br /&gt;
: Accurate records of changes are recorded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What can AWS config do =&lt;br /&gt;
&lt;br /&gt;
* Checks configurations &lt;br /&gt;
&lt;br /&gt;
* Can save a snapshot of the current configuration&lt;br /&gt;
&lt;br /&gt;
* Lets you pull historical configurations&lt;br /&gt;
&lt;br /&gt;
* Allows the viewing of relationships&lt;br /&gt;
&lt;br /&gt;
* Can find resources been used easily and quickly&lt;br /&gt;
&lt;br /&gt;
* Can help reduce troubleshooting times though the comparison with the last known good configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Does AWS config have associated charges =&lt;br /&gt;
&lt;br /&gt;
* Yes - recoding has two different prices for continuous and periodic recording.&lt;br /&gt;
&lt;br /&gt;
* Rule evaulations will also cost you.&lt;br /&gt;
&lt;br /&gt;
* How to avoid pricing:&lt;br /&gt;
&lt;br /&gt;
:* Exclude resources you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Filter out regions or systems you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Monitor your bill!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= How AWS Config works =&lt;br /&gt;
&lt;br /&gt;
When a service is started AWS config scans the account for supported resources or services.&lt;br /&gt;
&lt;br /&gt;
: A configuation item is created for each resource or service.&lt;br /&gt;
&lt;br /&gt;
: Each time a change takes place a new configuration item is created.&lt;br /&gt;
&lt;br /&gt;
:: This allows changes to be determined in the configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Items ==&lt;br /&gt;
&lt;br /&gt;
These are snapshots that are stored in JSON format.&lt;br /&gt;
&lt;br /&gt;
: They represent the configuration at a point in time.&lt;br /&gt;
&lt;br /&gt;
: Most resources are supported by AWS Config - but not all.&lt;br /&gt;
&lt;br /&gt;
: An updare to the CI is made every time something changes on a monitored resource.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inside a configuration item:&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Metadata&#039;&#039; - Information about the configuration item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Attributes&#039;&#039; - Resourde data of the configuraton item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Relationship&#039;&#039; - Holds related data:&lt;br /&gt;
&lt;br /&gt;
:: For example subnet infomation or VPC infomation.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Current configuration&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Confguration recorder ==&lt;br /&gt;
&lt;br /&gt;
The configuration recorder discoveres changes in resources, new or existing.&lt;br /&gt;
&lt;br /&gt;
: These changes are then fed into configration item.&lt;br /&gt;
&lt;br /&gt;
: A configuration recorder is a must to monitor configurations.&lt;br /&gt;
&lt;br /&gt;
: The configuration recorder is the eyes of the config system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The recorder can be setup severa ways:&lt;br /&gt;
&lt;br /&gt;
:* Command line interface &lt;br /&gt;
&lt;br /&gt;
:* IaC - Infrastrcture as code such as:&lt;br /&gt;
&lt;br /&gt;
::* CloudFormation&lt;br /&gt;
&lt;br /&gt;
::* Terraform&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default this will setup configuration items for all resources by defauly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration role ==&lt;br /&gt;
&lt;br /&gt;
This is an IAM role that provides read only access to record the configuration items.&lt;br /&gt;
&lt;br /&gt;
This role also needs write permissions to the S3 bucket where the snapshots will be stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration streams ==&lt;br /&gt;
&lt;br /&gt;
When a new configuration item is created it&#039;s added to a configuration stream.&lt;br /&gt;
&lt;br /&gt;
The configuration stream is the same as an SNS topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Basic Setup =&lt;br /&gt;
&lt;br /&gt;
This provides a overview, for the exact CLI commands consult the AWS guides.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Create an S3 bucket to store the configuration items&lt;br /&gt;
&lt;br /&gt;
* Create an SNS topic for the config service&lt;br /&gt;
&lt;br /&gt;
* Create the IAM role for the config service:&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
  &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
    { &lt;br /&gt;
      &amp;quot;Sid&amp;quot;: &amp;quot;AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
      &amp;quot;Principal&amp;quot;: { &lt;br /&gt;
        &amp;quot;Service&amp;quot;: &amp;quot;config.amazonaws.com&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      &amp;quot;Action&amp;quot;: &amp;quot;sts:AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Condition&amp;quot;: { &lt;br /&gt;
   &amp;quot;StringEquals&amp;quot;: { &lt;br /&gt;
     &amp;quot;AWS:SourceAccount&amp;quot;: &amp;quot;your account number&amp;quot; &lt;br /&gt;
   } &lt;br /&gt;
      } &lt;br /&gt;
   } &lt;br /&gt;
 ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Saving this will give you a role ARN - &#039;&#039;&#039;&#039;This will be needed to start the configuration recorder&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
lets break the JSON down for better understanding:&lt;br /&gt;
&lt;br /&gt;
:* You want to &#039;&#039;Assume a role&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To &#039;&#039;Allow&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* The &#039;&#039;Config service&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To access &#039;&#039;Your aws account&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;Policy&#039;&#039;&#039; now needs to be created for the role to use, lets use this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
     &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
     &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
      { &lt;br /&gt;
        &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3PutPolicy&amp;quot;,&amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::packt-config/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &amp;quot;s3:GetBucketAcl&amp;quot; ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:aws:s3::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigSNSPolicy&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;: &amp;quot;sns:Publish&amp;quot;, &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:&#039;&#039;&#039;SNS-ARN&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;DescribeResources&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
         &amp;quot;ec2:Describe*&amp;quot;&lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot; &lt;br /&gt;
      } &lt;br /&gt;
    ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Let&#039;s break the JSON down for understanding:&lt;br /&gt;
&lt;br /&gt;
:* It provides access to the bucket to write objects&lt;br /&gt;
&lt;br /&gt;
:* It provides assess to SNS for push data&lt;br /&gt;
&lt;br /&gt;
:* It allows allows the discerption of ec2 resources &lt;br /&gt;
&lt;br /&gt;
The entire process is captured:&lt;br /&gt;
&lt;br /&gt;
: Describe &amp;gt; Transmit (SNS) &amp;gt; Save (s3)&lt;br /&gt;
&lt;br /&gt;
With this done we can attach the policy to the role:&lt;br /&gt;
&lt;br /&gt;
This can be done in the AWS CLI with the following command:&lt;br /&gt;
&lt;br /&gt;
 aws iam attach-role-policy --role-name &#039;&#039;&#039;role name&#039;&#039;&#039; --policy-arn &#039;&#039;&#039;policy arn&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next and very importantly we need to determine what resources to capture.&lt;br /&gt;
&lt;br /&gt;
:* Keep in mind you will pay a nominal free for these / but this is AWS - resources add up $$$&lt;br /&gt;
&lt;br /&gt;
:* If you monitor too little you won&#039;t get the data you need to make decisions or protect the system.&lt;br /&gt;
&lt;br /&gt;
:* Decide what is right for your system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of the JSON file:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
           &amp;quot;allSupported&amp;quot;: false, &lt;br /&gt;
           &amp;quot;includeGlobalResourceTypes&amp;quot;: false, &lt;br /&gt;
           &amp;quot;resourceTypes&amp;quot;: [ &lt;br /&gt;
                   &amp;quot;AWS::EC2::SecurityGroup&amp;quot;, &lt;br /&gt;
                   &amp;quot;AWS::EC2::Volume&amp;quot; &lt;br /&gt;
           ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will monitor:&lt;br /&gt;
&lt;br /&gt;
::* EC2 security groups.&lt;br /&gt;
&lt;br /&gt;
::* EC2 Volue status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next create a delivery file:&lt;br /&gt;
&lt;br /&gt;
{ &lt;br /&gt;
           &amp;quot;name&amp;quot;: &amp;quot;default&amp;quot;, &lt;br /&gt;
           &amp;quot;s3BucketName&amp;quot;: &amp;quot;&#039;&#039;your-bucket&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;snsTopicARN&amp;quot;: &amp;quot;arn:aws:sns:&#039;&#039;your-sns&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;configSnapshotDeliveryProperties&amp;quot;: { &lt;br /&gt;
               &amp;quot;deliveryFrequency&amp;quot;: &amp;quot;Twelve_Hours&amp;quot; &lt;br /&gt;
           } &lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
::* Connects the S3 bucket&lt;br /&gt;
&lt;br /&gt;
::* Connects the SNS&lt;br /&gt;
&lt;br /&gt;
::* Defines the frequency&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, start the recorder&lt;br /&gt;
&lt;br /&gt;
 aws configservice start-configuration-recorder --configuration-recorder-name &#039;&#039;name&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::* It will take a few minutes for the data to be posted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AWS Config Rules =&lt;br /&gt;
&lt;br /&gt;
Rules enable you to automatically evaluate the configuration of monitored resources.&lt;br /&gt;
&lt;br /&gt;
A rule can be triggered in two ways:&lt;br /&gt;
&lt;br /&gt;
:* When a resource changes&lt;br /&gt;
&lt;br /&gt;
:* On a schedule&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These rules allow you to enfore a consistant approach to AWS resources.&lt;br /&gt;
&lt;br /&gt;
: This is independent of who deployed them or when they where deployed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rules can apply to ==&lt;br /&gt;
&lt;br /&gt;
:* A single or a set of resouce ID&#039;s&lt;br /&gt;
&lt;br /&gt;
:* Types of resources &lt;br /&gt;
&lt;br /&gt;
:* Resources with a specified tag&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rules help enforce compliance.&lt;br /&gt;
&lt;br /&gt;
: Labmba functions can also be used to add logic to the rules.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AWS Config Managed Rules ==&lt;br /&gt;
&lt;br /&gt;
These are preconfigured to ensure your systems comply to industry best practices.&lt;br /&gt;
&lt;br /&gt;
For custom rules their is no need for write an action - it is performed automatically.&lt;br /&gt;
&lt;br /&gt;
Over 150 managed rules exist today.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Custom Rules ==&lt;br /&gt;
&lt;br /&gt;
Custom rules can be created using two methods:&lt;br /&gt;
&lt;br /&gt;
:* AWS Lambda &lt;br /&gt;
&lt;br /&gt;
:* A Guard policy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rule Evaluation ==&lt;br /&gt;
&lt;br /&gt;
:* Proactive mode - Immimdate evaluation&lt;br /&gt;
&lt;br /&gt;
:* Detective mode - Evaulated against resources that are already depoyed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conformance packs ==&lt;br /&gt;
&lt;br /&gt;
:* These make it easy to implement best practices.&lt;br /&gt;
&lt;br /&gt;
:* Can be run in a region or over multiple regions via aggregator.&lt;br /&gt;
&lt;br /&gt;
:* Enables a one click setup.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides&amp;diff=1611</id>
		<title>Study Guides</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides&amp;diff=1611"/>
		<updated>2026-05-21T15:46:24Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=SCS-C02 Cybersecurity Speaclity=&lt;br /&gt;
&lt;br /&gt;
📗[[Study Guides/AWS Cybersecurity Notes]]&lt;br /&gt;
&lt;br /&gt;
=Multiple Choice Guide=&lt;br /&gt;
&lt;br /&gt;
✅[https://www.dmu.edu/wp-content/uploads/MULTIPLE-CHOICE-TEST-TAKING-STRATEGIES.pdf Hacking Multiple Choice Questions]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=AWS_Cybersecurity_Notes&amp;diff=1610</id>
		<title>AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=AWS_Cybersecurity_Notes&amp;diff=1610"/>
		<updated>2026-05-21T15:45:43Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Mflavell moved page AWS Cybersecurity Notes to Study Guides/AWS Cybersecurity Notes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Study Guides/AWS Cybersecurity Notes]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1609</id>
		<title>Study Guides/AWS Cybersecurity Notes</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes&amp;diff=1609"/>
		<updated>2026-05-21T15:45:42Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Mflavell moved page AWS Cybersecurity Notes to Study Guides/AWS Cybersecurity Notes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Study Guides]] &amp;gt; AWS Cybersecurity Notes&lt;br /&gt;
&lt;br /&gt;
=SCS-C02=&lt;br /&gt;
&lt;br /&gt;
[https://a.co/d/7oZWHFl 📕Recommended Study Guide]&lt;br /&gt;
&lt;br /&gt;
[[AWS - Cloudtrail]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 2]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 3]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 4]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 5]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 6]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 7]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Certified Serucity Spacaility - SCS-C02 Study notes - Part 8]]&lt;br /&gt;
&lt;br /&gt;
[[Building a Bastion server - Part 9]]&lt;br /&gt;
&lt;br /&gt;
[[Isolating EC2 Instances for Forensic Inspection]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Detective]]&lt;br /&gt;
&lt;br /&gt;
[[Systems Manager]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon Inspector]]&lt;br /&gt;
&lt;br /&gt;
[[Amazon KMS]]&lt;br /&gt;
&lt;br /&gt;
[[Cloud HSM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS IAM]]&lt;br /&gt;
&lt;br /&gt;
[[AWS Config]]&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1608</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1608"/>
		<updated>2026-05-21T15:39:37Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Cramsession Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
=== Do no harm ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;👉Breaking these will get you a lifetime ban&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Help each other on our journey ===&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== We are here... for all mankind ===&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Keep your author account in good standing ===&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1607</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Config</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1607"/>
		<updated>2026-05-20T00:46:31Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* AWS Config Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Study Guides]] &amp;gt; [[AWS Cybersecurity Notes]] &amp;gt; AWS Config&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What is AWS Config =&lt;br /&gt;
&lt;br /&gt;
AWS Config - records configurations and configuration changes.&lt;br /&gt;
&lt;br /&gt;
This is separate from cloud trail that records user events.&lt;br /&gt;
&lt;br /&gt;
: How to visualize this&lt;br /&gt;
&lt;br /&gt;
:: Peope leave trails 🚶... (Cloud Trail)&lt;br /&gt;
&lt;br /&gt;
:: Computers have configuration&lt;br /&gt;
&lt;br /&gt;
::: Cloudtrail = Who did it?&lt;br /&gt;
&lt;br /&gt;
::: AWS Config = What did they do?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS config has a &#039;&#039;configuration recorder&#039;&#039; that lets you inventory in real time.&lt;br /&gt;
&lt;br /&gt;
:: Can be used in across multiple regions or accounts.&lt;br /&gt;
&lt;br /&gt;
:: Resources can be evaluated constantly or on a fixed schedule.&lt;br /&gt;
&lt;br /&gt;
:: Lambda or System manager can be used to automatically remediate any compliance problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config allows a system to be continuously compliant by maintaining records of the systems sin&lt;br /&gt;
&lt;br /&gt;
:: Any time a change is made on the system - the change is captured with who or what made the change.&lt;br /&gt;
&lt;br /&gt;
:: This enabled auditing and checking of compliance levels at any time, on demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Why use AWS config =&lt;br /&gt;
&lt;br /&gt;
It is hard to understand what resources you are using in AWS.&lt;br /&gt;
&lt;br /&gt;
: Think of the problems running a massive system.&lt;br /&gt;
&lt;br /&gt;
:: How can you ever keep up with the what / where?&lt;br /&gt;
&lt;br /&gt;
:: How do you know what is no longer required?&lt;br /&gt;
&lt;br /&gt;
:: How do you know developers and engineers are following security policy?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for risk reduction:&lt;br /&gt;
&lt;br /&gt;
: Checking server exposure to the internet&lt;br /&gt;
&lt;br /&gt;
: Volumes that may not be encrypted.&lt;br /&gt;
&lt;br /&gt;
: Servers than hardening.&lt;br /&gt;
&lt;br /&gt;
: Accurate records of changes are recorded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What can AWS config do =&lt;br /&gt;
&lt;br /&gt;
* Checks configurations &lt;br /&gt;
&lt;br /&gt;
* Can save a snapshot of the current configuration&lt;br /&gt;
&lt;br /&gt;
* Lets you pull historical configurations&lt;br /&gt;
&lt;br /&gt;
* Allows the viewing of relationships&lt;br /&gt;
&lt;br /&gt;
* Can find resources been used easily and quickly&lt;br /&gt;
&lt;br /&gt;
* Can help reduce troubleshooting times though the comparison with the last known good configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Does AWS config have associated charges =&lt;br /&gt;
&lt;br /&gt;
* Yes - recoding has two different prices for continuous and periodic recording.&lt;br /&gt;
&lt;br /&gt;
* Rule evaulations will also cost you.&lt;br /&gt;
&lt;br /&gt;
* How to avoid pricing:&lt;br /&gt;
&lt;br /&gt;
:* Exclude resources you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Filter out regions or systems you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Monitor your bill!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= How AWS Config works =&lt;br /&gt;
&lt;br /&gt;
When a service is started AWS config scans the account for supported resources or services.&lt;br /&gt;
&lt;br /&gt;
: A configuation item is created for each resource or service.&lt;br /&gt;
&lt;br /&gt;
: Each time a change takes place a new configuration item is created.&lt;br /&gt;
&lt;br /&gt;
:: This allows changes to be determined in the configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Items ==&lt;br /&gt;
&lt;br /&gt;
These are snapshots that are stored in JSON format.&lt;br /&gt;
&lt;br /&gt;
: They represent the configuration at a point in time.&lt;br /&gt;
&lt;br /&gt;
: Most resources are supported by AWS Config - but not all.&lt;br /&gt;
&lt;br /&gt;
: An updare to the CI is made every time something changes on a monitored resource.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inside a configuration item:&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Metadata&#039;&#039; - Information about the configuration item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Attributes&#039;&#039; - Resourde data of the configuraton item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Relationship&#039;&#039; - Holds related data:&lt;br /&gt;
&lt;br /&gt;
:: For example subnet infomation or VPC infomation.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Current configuration&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Confguration recorder ==&lt;br /&gt;
&lt;br /&gt;
The configuration recorder discoveres changes in resources, new or existing.&lt;br /&gt;
&lt;br /&gt;
: These changes are then fed into configration item.&lt;br /&gt;
&lt;br /&gt;
: A configuration recorder is a must to monitor configurations.&lt;br /&gt;
&lt;br /&gt;
: The configuration recorder is the eyes of the config system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The recorder can be setup severa ways:&lt;br /&gt;
&lt;br /&gt;
:* Command line interface &lt;br /&gt;
&lt;br /&gt;
:* IaC - Infrastrcture as code such as:&lt;br /&gt;
&lt;br /&gt;
::* CloudFormation&lt;br /&gt;
&lt;br /&gt;
::* Terraform&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default this will setup configuration items for all resources by defauly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration role ==&lt;br /&gt;
&lt;br /&gt;
This is an IAM role that provides read only access to record the configuration items.&lt;br /&gt;
&lt;br /&gt;
This role also needs write permissions to the S3 bucket where the snapshots will be stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration streams ==&lt;br /&gt;
&lt;br /&gt;
When a new configuration item is created it&#039;s added to a configuration stream.&lt;br /&gt;
&lt;br /&gt;
The configuration stream is the same as an SNS topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Basic Setup =&lt;br /&gt;
&lt;br /&gt;
This provides a overview, for the exact CLI commands consult the AWS guides.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Create an S3 bucket to store the configuration items&lt;br /&gt;
&lt;br /&gt;
* Create an SNS topic for the config service&lt;br /&gt;
&lt;br /&gt;
* Create the IAM role for the config service:&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
  &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
    { &lt;br /&gt;
      &amp;quot;Sid&amp;quot;: &amp;quot;AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
      &amp;quot;Principal&amp;quot;: { &lt;br /&gt;
        &amp;quot;Service&amp;quot;: &amp;quot;config.amazonaws.com&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      &amp;quot;Action&amp;quot;: &amp;quot;sts:AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Condition&amp;quot;: { &lt;br /&gt;
   &amp;quot;StringEquals&amp;quot;: { &lt;br /&gt;
     &amp;quot;AWS:SourceAccount&amp;quot;: &amp;quot;your account number&amp;quot; &lt;br /&gt;
   } &lt;br /&gt;
      } &lt;br /&gt;
   } &lt;br /&gt;
 ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Saving this will give you a role ARN - &#039;&#039;&#039;&#039;This will be needed to start the configuration recorder&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
lets break the JSON down for better understanding:&lt;br /&gt;
&lt;br /&gt;
:* You want to &#039;&#039;Assume a role&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To &#039;&#039;Allow&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* The &#039;&#039;Config service&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To access &#039;&#039;Your aws account&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;Policy&#039;&#039;&#039; now needs to be created for the role to use, lets use this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
     &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
     &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
      { &lt;br /&gt;
        &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3PutPolicy&amp;quot;,&amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::packt-config/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &amp;quot;s3:GetBucketAcl&amp;quot; ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:aws:s3::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigSNSPolicy&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;: &amp;quot;sns:Publish&amp;quot;, &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:&#039;&#039;&#039;SNS-ARN&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;DescribeResources&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
         &amp;quot;ec2:Describe*&amp;quot;&lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot; &lt;br /&gt;
      } &lt;br /&gt;
    ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Let&#039;s break the JSON down for understanding:&lt;br /&gt;
&lt;br /&gt;
:* It provides access to the bucket to write objects&lt;br /&gt;
&lt;br /&gt;
:* It provides assess to SNS for push data&lt;br /&gt;
&lt;br /&gt;
:* It allows allows the discerption of ec2 resources &lt;br /&gt;
&lt;br /&gt;
The entire process is captured:&lt;br /&gt;
&lt;br /&gt;
: Describe &amp;gt; Transmit (SNS) &amp;gt; Save (s3)&lt;br /&gt;
&lt;br /&gt;
With this done we can attach the policy to the role:&lt;br /&gt;
&lt;br /&gt;
This can be done in the AWS CLI with the following command:&lt;br /&gt;
&lt;br /&gt;
 aws iam attach-role-policy --role-name &#039;&#039;&#039;role name&#039;&#039;&#039; --policy-arn &#039;&#039;&#039;policy arn&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next and very importantly we need to determine what resources to capture.&lt;br /&gt;
&lt;br /&gt;
:* Keep in mind you will pay a nominal free for these / but this is AWS - resources add up $$$&lt;br /&gt;
&lt;br /&gt;
:* If you monitor too little you won&#039;t get the data you need to make decisions or protect the system.&lt;br /&gt;
&lt;br /&gt;
:* Decide what is right for your system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of the JSON file:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
           &amp;quot;allSupported&amp;quot;: false, &lt;br /&gt;
           &amp;quot;includeGlobalResourceTypes&amp;quot;: false, &lt;br /&gt;
           &amp;quot;resourceTypes&amp;quot;: [ &lt;br /&gt;
                   &amp;quot;AWS::EC2::SecurityGroup&amp;quot;, &lt;br /&gt;
                   &amp;quot;AWS::EC2::Volume&amp;quot; &lt;br /&gt;
           ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will monitor:&lt;br /&gt;
&lt;br /&gt;
::* EC2 security groups.&lt;br /&gt;
&lt;br /&gt;
::* EC2 Volue status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next create a delivery file:&lt;br /&gt;
&lt;br /&gt;
{ &lt;br /&gt;
           &amp;quot;name&amp;quot;: &amp;quot;default&amp;quot;, &lt;br /&gt;
           &amp;quot;s3BucketName&amp;quot;: &amp;quot;&#039;&#039;your-bucket&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;snsTopicARN&amp;quot;: &amp;quot;arn:aws:sns:&#039;&#039;your-sns&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;configSnapshotDeliveryProperties&amp;quot;: { &lt;br /&gt;
               &amp;quot;deliveryFrequency&amp;quot;: &amp;quot;Twelve_Hours&amp;quot; &lt;br /&gt;
           } &lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
::* Connects the S3 bucket&lt;br /&gt;
&lt;br /&gt;
::* Connects the SNS&lt;br /&gt;
&lt;br /&gt;
::* Defines the frequency&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, start the recorder&lt;br /&gt;
&lt;br /&gt;
 aws configservice start-configuration-recorder --configuration-recorder-name &#039;&#039;name&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::* It will take a few minutes for the data to be posted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AWS Config Rules =&lt;br /&gt;
&lt;br /&gt;
Rules enable you to automatically evaluate the configuration of monitored resources.&lt;br /&gt;
&lt;br /&gt;
A rule can be triggered in two ways:&lt;br /&gt;
&lt;br /&gt;
:* When a resource changes&lt;br /&gt;
&lt;br /&gt;
:* On a schedule&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These rules allow you to enfore a consistant approach to AWS resources.&lt;br /&gt;
&lt;br /&gt;
: This is independent of who deployed them or when they where deployed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rules can apply to ==&lt;br /&gt;
&lt;br /&gt;
:* A single or a set of resouce ID&#039;s&lt;br /&gt;
&lt;br /&gt;
:* Types of resources &lt;br /&gt;
&lt;br /&gt;
:* Resources with a specified tag&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rules help enforce compliance.&lt;br /&gt;
&lt;br /&gt;
: Labmba functions can also be used to add logic to the rules.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AWS Config Managed Rules ==&lt;br /&gt;
&lt;br /&gt;
These are preconfigured to ensure your systems comply to industry best practices.&lt;br /&gt;
&lt;br /&gt;
For custom rules their is no need for write an action - it is performed automatically.&lt;br /&gt;
&lt;br /&gt;
Over 150 managed rules exist today.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Custom Rules ==&lt;br /&gt;
&lt;br /&gt;
Custom rules can be created using two methods:&lt;br /&gt;
&lt;br /&gt;
:* AWS Lambda &lt;br /&gt;
&lt;br /&gt;
:* A Guard policy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rule Evaluation ==&lt;br /&gt;
&lt;br /&gt;
:* Proactive mode - Immimdate evaluation&lt;br /&gt;
&lt;br /&gt;
:* Detective mode - Evaulated against resources that are already depoyed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conformance packs ==&lt;br /&gt;
&lt;br /&gt;
:* These make it easy to implement best practices.&lt;br /&gt;
&lt;br /&gt;
:* Can be run in a region or over multiple regions via aggregator.&lt;br /&gt;
&lt;br /&gt;
:* Enables a one click setup.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1606</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Config</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1606"/>
		<updated>2026-05-20T00:36:12Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* AWS Config Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Study Guides]] &amp;gt; [[AWS Cybersecurity Notes]] &amp;gt; AWS Config&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What is AWS Config =&lt;br /&gt;
&lt;br /&gt;
AWS Config - records configurations and configuration changes.&lt;br /&gt;
&lt;br /&gt;
This is separate from cloud trail that records user events.&lt;br /&gt;
&lt;br /&gt;
: How to visualize this&lt;br /&gt;
&lt;br /&gt;
:: Peope leave trails 🚶... (Cloud Trail)&lt;br /&gt;
&lt;br /&gt;
:: Computers have configuration&lt;br /&gt;
&lt;br /&gt;
::: Cloudtrail = Who did it?&lt;br /&gt;
&lt;br /&gt;
::: AWS Config = What did they do?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS config has a &#039;&#039;configuration recorder&#039;&#039; that lets you inventory in real time.&lt;br /&gt;
&lt;br /&gt;
:: Can be used in across multiple regions or accounts.&lt;br /&gt;
&lt;br /&gt;
:: Resources can be evaluated constantly or on a fixed schedule.&lt;br /&gt;
&lt;br /&gt;
:: Lambda or System manager can be used to automatically remediate any compliance problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config allows a system to be continuously compliant by maintaining records of the systems sin&lt;br /&gt;
&lt;br /&gt;
:: Any time a change is made on the system - the change is captured with who or what made the change.&lt;br /&gt;
&lt;br /&gt;
:: This enabled auditing and checking of compliance levels at any time, on demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Why use AWS config =&lt;br /&gt;
&lt;br /&gt;
It is hard to understand what resources you are using in AWS.&lt;br /&gt;
&lt;br /&gt;
: Think of the problems running a massive system.&lt;br /&gt;
&lt;br /&gt;
:: How can you ever keep up with the what / where?&lt;br /&gt;
&lt;br /&gt;
:: How do you know what is no longer required?&lt;br /&gt;
&lt;br /&gt;
:: How do you know developers and engineers are following security policy?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for risk reduction:&lt;br /&gt;
&lt;br /&gt;
: Checking server exposure to the internet&lt;br /&gt;
&lt;br /&gt;
: Volumes that may not be encrypted.&lt;br /&gt;
&lt;br /&gt;
: Servers than hardening.&lt;br /&gt;
&lt;br /&gt;
: Accurate records of changes are recorded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What can AWS config do =&lt;br /&gt;
&lt;br /&gt;
* Checks configurations &lt;br /&gt;
&lt;br /&gt;
* Can save a snapshot of the current configuration&lt;br /&gt;
&lt;br /&gt;
* Lets you pull historical configurations&lt;br /&gt;
&lt;br /&gt;
* Allows the viewing of relationships&lt;br /&gt;
&lt;br /&gt;
* Can find resources been used easily and quickly&lt;br /&gt;
&lt;br /&gt;
* Can help reduce troubleshooting times though the comparison with the last known good configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Does AWS config have associated charges =&lt;br /&gt;
&lt;br /&gt;
* Yes - recoding has two different prices for continuous and periodic recording.&lt;br /&gt;
&lt;br /&gt;
* Rule evaulations will also cost you.&lt;br /&gt;
&lt;br /&gt;
* How to avoid pricing:&lt;br /&gt;
&lt;br /&gt;
:* Exclude resources you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Filter out regions or systems you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Monitor your bill!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= How AWS Config works =&lt;br /&gt;
&lt;br /&gt;
When a service is started AWS config scans the account for supported resources or services.&lt;br /&gt;
&lt;br /&gt;
: A configuation item is created for each resource or service.&lt;br /&gt;
&lt;br /&gt;
: Each time a change takes place a new configuration item is created.&lt;br /&gt;
&lt;br /&gt;
:: This allows changes to be determined in the configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Items ==&lt;br /&gt;
&lt;br /&gt;
These are snapshots that are stored in JSON format.&lt;br /&gt;
&lt;br /&gt;
: They represent the configuration at a point in time.&lt;br /&gt;
&lt;br /&gt;
: Most resources are supported by AWS Config - but not all.&lt;br /&gt;
&lt;br /&gt;
: An updare to the CI is made every time something changes on a monitored resource.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inside a configuration item:&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Metadata&#039;&#039; - Information about the configuration item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Attributes&#039;&#039; - Resourde data of the configuraton item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Relationship&#039;&#039; - Holds related data:&lt;br /&gt;
&lt;br /&gt;
:: For example subnet infomation or VPC infomation.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Current configuration&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Confguration recorder ==&lt;br /&gt;
&lt;br /&gt;
The configuration recorder discoveres changes in resources, new or existing.&lt;br /&gt;
&lt;br /&gt;
: These changes are then fed into configration item.&lt;br /&gt;
&lt;br /&gt;
: A configuration recorder is a must to monitor configurations.&lt;br /&gt;
&lt;br /&gt;
: The configuration recorder is the eyes of the config system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The recorder can be setup severa ways:&lt;br /&gt;
&lt;br /&gt;
:* Command line interface &lt;br /&gt;
&lt;br /&gt;
:* IaC - Infrastrcture as code such as:&lt;br /&gt;
&lt;br /&gt;
::* CloudFormation&lt;br /&gt;
&lt;br /&gt;
::* Terraform&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default this will setup configuration items for all resources by defauly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration role ==&lt;br /&gt;
&lt;br /&gt;
This is an IAM role that provides read only access to record the configuration items.&lt;br /&gt;
&lt;br /&gt;
This role also needs write permissions to the S3 bucket where the snapshots will be stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration streams ==&lt;br /&gt;
&lt;br /&gt;
When a new configuration item is created it&#039;s added to a configuration stream.&lt;br /&gt;
&lt;br /&gt;
The configuration stream is the same as an SNS topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Basic Setup =&lt;br /&gt;
&lt;br /&gt;
This provides a overview, for the exact CLI commands consult the AWS guides.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Create an S3 bucket to store the configuration items&lt;br /&gt;
&lt;br /&gt;
* Create an SNS topic for the config service&lt;br /&gt;
&lt;br /&gt;
* Create the IAM role for the config service:&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
  &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
    { &lt;br /&gt;
      &amp;quot;Sid&amp;quot;: &amp;quot;AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
      &amp;quot;Principal&amp;quot;: { &lt;br /&gt;
        &amp;quot;Service&amp;quot;: &amp;quot;config.amazonaws.com&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      &amp;quot;Action&amp;quot;: &amp;quot;sts:AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Condition&amp;quot;: { &lt;br /&gt;
   &amp;quot;StringEquals&amp;quot;: { &lt;br /&gt;
     &amp;quot;AWS:SourceAccount&amp;quot;: &amp;quot;your account number&amp;quot; &lt;br /&gt;
   } &lt;br /&gt;
      } &lt;br /&gt;
   } &lt;br /&gt;
 ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Saving this will give you a role ARN - &#039;&#039;&#039;&#039;This will be needed to start the configuration recorder&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
lets break the JSON down for better understanding:&lt;br /&gt;
&lt;br /&gt;
:* You want to &#039;&#039;Assume a role&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To &#039;&#039;Allow&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* The &#039;&#039;Config service&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To access &#039;&#039;Your aws account&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;Policy&#039;&#039;&#039; now needs to be created for the role to use, lets use this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
     &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
     &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
      { &lt;br /&gt;
        &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3PutPolicy&amp;quot;,&amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::packt-config/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &amp;quot;s3:GetBucketAcl&amp;quot; ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:aws:s3::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigSNSPolicy&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;: &amp;quot;sns:Publish&amp;quot;, &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:&#039;&#039;&#039;SNS-ARN&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;DescribeResources&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
         &amp;quot;ec2:Describe*&amp;quot;&lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot; &lt;br /&gt;
      } &lt;br /&gt;
    ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Let&#039;s break the JSON down for understanding:&lt;br /&gt;
&lt;br /&gt;
:* It provides access to the bucket to write objects&lt;br /&gt;
&lt;br /&gt;
:* It provides assess to SNS for push data&lt;br /&gt;
&lt;br /&gt;
:* It allows allows the discerption of ec2 resources &lt;br /&gt;
&lt;br /&gt;
The entire process is captured:&lt;br /&gt;
&lt;br /&gt;
: Describe &amp;gt; Transmit (SNS) &amp;gt; Save (s3)&lt;br /&gt;
&lt;br /&gt;
With this done we can attach the policy to the role:&lt;br /&gt;
&lt;br /&gt;
This can be done in the AWS CLI with the following command:&lt;br /&gt;
&lt;br /&gt;
 aws iam attach-role-policy --role-name &#039;&#039;&#039;role name&#039;&#039;&#039; --policy-arn &#039;&#039;&#039;policy arn&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next and very importantly we need to determine what resources to capture.&lt;br /&gt;
&lt;br /&gt;
:* Keep in mind you will pay a nominal free for these / but this is AWS - resources add up $$$&lt;br /&gt;
&lt;br /&gt;
:* If you monitor too little you won&#039;t get the data you need to make decisions or protect the system.&lt;br /&gt;
&lt;br /&gt;
:* Decide what is right for your system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of the JSON file:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
           &amp;quot;allSupported&amp;quot;: false, &lt;br /&gt;
           &amp;quot;includeGlobalResourceTypes&amp;quot;: false, &lt;br /&gt;
           &amp;quot;resourceTypes&amp;quot;: [ &lt;br /&gt;
                   &amp;quot;AWS::EC2::SecurityGroup&amp;quot;, &lt;br /&gt;
                   &amp;quot;AWS::EC2::Volume&amp;quot; &lt;br /&gt;
           ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will monitor:&lt;br /&gt;
&lt;br /&gt;
::* EC2 security groups.&lt;br /&gt;
&lt;br /&gt;
::* EC2 Volue status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next create a delivery file:&lt;br /&gt;
&lt;br /&gt;
{ &lt;br /&gt;
           &amp;quot;name&amp;quot;: &amp;quot;default&amp;quot;, &lt;br /&gt;
           &amp;quot;s3BucketName&amp;quot;: &amp;quot;&#039;&#039;your-bucket&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;snsTopicARN&amp;quot;: &amp;quot;arn:aws:sns:&#039;&#039;your-sns&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;configSnapshotDeliveryProperties&amp;quot;: { &lt;br /&gt;
               &amp;quot;deliveryFrequency&amp;quot;: &amp;quot;Twelve_Hours&amp;quot; &lt;br /&gt;
           } &lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
::* Connects the S3 bucket&lt;br /&gt;
&lt;br /&gt;
::* Connects the SNS&lt;br /&gt;
&lt;br /&gt;
::* Defines the frequency&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, start the recorder&lt;br /&gt;
&lt;br /&gt;
 aws configservice start-configuration-recorder --configuration-recorder-name &#039;&#039;name&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::* It will take a few minutes for the data to be posted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AWS Config Rules =&lt;br /&gt;
&lt;br /&gt;
Rules enable you to automatically evaluate the configuration of monitored resources.&lt;br /&gt;
&lt;br /&gt;
A rule can be triggered in two ways:&lt;br /&gt;
&lt;br /&gt;
:* When a resource changes&lt;br /&gt;
&lt;br /&gt;
:* On a schedule&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These rules allow you to enfore a consistant approach to AWS resources.&lt;br /&gt;
&lt;br /&gt;
: This is independent of who deployed them or when they where deployed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rules can apply to ==&lt;br /&gt;
&lt;br /&gt;
:* A single or a set of resouce ID&#039;s&lt;br /&gt;
&lt;br /&gt;
:* Types of resources &lt;br /&gt;
&lt;br /&gt;
:* Resources with a specified tag&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rules help enforce compliance.&lt;br /&gt;
&lt;br /&gt;
: Labmba functions can also be used to add logic to the rules.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AWS Config Managed Rules ==&lt;br /&gt;
&lt;br /&gt;
These are preconfigured to ensure your systems comply to industry best practices.&lt;br /&gt;
&lt;br /&gt;
For custom rules their is no need for write an action - it is performed automatically.&lt;br /&gt;
&lt;br /&gt;
Over 150 managed rules exist today.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Custom Rules ==&lt;br /&gt;
&lt;br /&gt;
Custom rules can be created using two methods:&lt;br /&gt;
&lt;br /&gt;
:* AWS Lambda &lt;br /&gt;
&lt;br /&gt;
:* A Guard policy&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1605</id>
		<title>Study Guides/AWS Cybersecurity Notes/AWS Config</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Study_Guides/AWS_Cybersecurity_Notes/AWS_Config&amp;diff=1605"/>
		<updated>2026-05-20T00:17:56Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Study Guides]] &amp;gt; [[AWS Cybersecurity Notes]] &amp;gt; AWS Config&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What is AWS Config =&lt;br /&gt;
&lt;br /&gt;
AWS Config - records configurations and configuration changes.&lt;br /&gt;
&lt;br /&gt;
This is separate from cloud trail that records user events.&lt;br /&gt;
&lt;br /&gt;
: How to visualize this&lt;br /&gt;
&lt;br /&gt;
:: Peope leave trails 🚶... (Cloud Trail)&lt;br /&gt;
&lt;br /&gt;
:: Computers have configuration&lt;br /&gt;
&lt;br /&gt;
::: Cloudtrail = Who did it?&lt;br /&gt;
&lt;br /&gt;
::: AWS Config = What did they do?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS config has a &#039;&#039;configuration recorder&#039;&#039; that lets you inventory in real time.&lt;br /&gt;
&lt;br /&gt;
:: Can be used in across multiple regions or accounts.&lt;br /&gt;
&lt;br /&gt;
:: Resources can be evaluated constantly or on a fixed schedule.&lt;br /&gt;
&lt;br /&gt;
:: Lambda or System manager can be used to automatically remediate any compliance problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AWS Config allows a system to be continuously compliant by maintaining records of the systems sin&lt;br /&gt;
&lt;br /&gt;
:: Any time a change is made on the system - the change is captured with who or what made the change.&lt;br /&gt;
&lt;br /&gt;
:: This enabled auditing and checking of compliance levels at any time, on demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Why use AWS config =&lt;br /&gt;
&lt;br /&gt;
It is hard to understand what resources you are using in AWS.&lt;br /&gt;
&lt;br /&gt;
: Think of the problems running a massive system.&lt;br /&gt;
&lt;br /&gt;
:: How can you ever keep up with the what / where?&lt;br /&gt;
&lt;br /&gt;
:: How do you know what is no longer required?&lt;br /&gt;
&lt;br /&gt;
:: How do you know developers and engineers are following security policy?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for risk reduction:&lt;br /&gt;
&lt;br /&gt;
: Checking server exposure to the internet&lt;br /&gt;
&lt;br /&gt;
: Volumes that may not be encrypted.&lt;br /&gt;
&lt;br /&gt;
: Servers than hardening.&lt;br /&gt;
&lt;br /&gt;
: Accurate records of changes are recorded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= What can AWS config do =&lt;br /&gt;
&lt;br /&gt;
* Checks configurations &lt;br /&gt;
&lt;br /&gt;
* Can save a snapshot of the current configuration&lt;br /&gt;
&lt;br /&gt;
* Lets you pull historical configurations&lt;br /&gt;
&lt;br /&gt;
* Allows the viewing of relationships&lt;br /&gt;
&lt;br /&gt;
* Can find resources been used easily and quickly&lt;br /&gt;
&lt;br /&gt;
* Can help reduce troubleshooting times though the comparison with the last known good configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Does AWS config have associated charges =&lt;br /&gt;
&lt;br /&gt;
* Yes - recoding has two different prices for continuous and periodic recording.&lt;br /&gt;
&lt;br /&gt;
* Rule evaulations will also cost you.&lt;br /&gt;
&lt;br /&gt;
* How to avoid pricing:&lt;br /&gt;
&lt;br /&gt;
:* Exclude resources you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Filter out regions or systems you don&#039;t care about.&lt;br /&gt;
&lt;br /&gt;
:* Monitor your bill!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= How AWS Config works =&lt;br /&gt;
&lt;br /&gt;
When a service is started AWS config scans the account for supported resources or services.&lt;br /&gt;
&lt;br /&gt;
: A configuation item is created for each resource or service.&lt;br /&gt;
&lt;br /&gt;
: Each time a change takes place a new configuration item is created.&lt;br /&gt;
&lt;br /&gt;
:: This allows changes to be determined in the configuration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration Items ==&lt;br /&gt;
&lt;br /&gt;
These are snapshots that are stored in JSON format.&lt;br /&gt;
&lt;br /&gt;
: They represent the configuration at a point in time.&lt;br /&gt;
&lt;br /&gt;
: Most resources are supported by AWS Config - but not all.&lt;br /&gt;
&lt;br /&gt;
: An updare to the CI is made every time something changes on a monitored resource.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Inside a configuration item:&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Metadata&#039;&#039; - Information about the configuration item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Attributes&#039;&#039; - Resourde data of the configuraton item.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Relationship&#039;&#039; - Holds related data:&lt;br /&gt;
&lt;br /&gt;
:: For example subnet infomation or VPC infomation.&lt;br /&gt;
&lt;br /&gt;
:* &#039;&#039;Current configuration&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Confguration recorder ==&lt;br /&gt;
&lt;br /&gt;
The configuration recorder discoveres changes in resources, new or existing.&lt;br /&gt;
&lt;br /&gt;
: These changes are then fed into configration item.&lt;br /&gt;
&lt;br /&gt;
: A configuration recorder is a must to monitor configurations.&lt;br /&gt;
&lt;br /&gt;
: The configuration recorder is the eyes of the config system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The recorder can be setup severa ways:&lt;br /&gt;
&lt;br /&gt;
:* Command line interface &lt;br /&gt;
&lt;br /&gt;
:* IaC - Infrastrcture as code such as:&lt;br /&gt;
&lt;br /&gt;
::* CloudFormation&lt;br /&gt;
&lt;br /&gt;
::* Terraform&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By default this will setup configuration items for all resources by defauly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration role ==&lt;br /&gt;
&lt;br /&gt;
This is an IAM role that provides read only access to record the configuration items.&lt;br /&gt;
&lt;br /&gt;
This role also needs write permissions to the S3 bucket where the snapshots will be stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Configuration streams ==&lt;br /&gt;
&lt;br /&gt;
When a new configuration item is created it&#039;s added to a configuration stream.&lt;br /&gt;
&lt;br /&gt;
The configuration stream is the same as an SNS topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Basic Setup =&lt;br /&gt;
&lt;br /&gt;
This provides a overview, for the exact CLI commands consult the AWS guides.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Create an S3 bucket to store the configuration items&lt;br /&gt;
&lt;br /&gt;
* Create an SNS topic for the config service&lt;br /&gt;
&lt;br /&gt;
* Create the IAM role for the config service:&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
  &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
  &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
    { &lt;br /&gt;
      &amp;quot;Sid&amp;quot;: &amp;quot;AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
      &amp;quot;Principal&amp;quot;: { &lt;br /&gt;
        &amp;quot;Service&amp;quot;: &amp;quot;config.amazonaws.com&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      &amp;quot;Action&amp;quot;: &amp;quot;sts:AssumeRole&amp;quot;, &lt;br /&gt;
      &amp;quot;Condition&amp;quot;: { &lt;br /&gt;
   &amp;quot;StringEquals&amp;quot;: { &lt;br /&gt;
     &amp;quot;AWS:SourceAccount&amp;quot;: &amp;quot;your account number&amp;quot; &lt;br /&gt;
   } &lt;br /&gt;
      } &lt;br /&gt;
   } &lt;br /&gt;
 ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Saving this will give you a role ARN - &#039;&#039;&#039;&#039;This will be needed to start the configuration recorder&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
lets break the JSON down for better understanding:&lt;br /&gt;
&lt;br /&gt;
:* You want to &#039;&#039;Assume a role&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To &#039;&#039;Allow&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* The &#039;&#039;Config service&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* To access &#039;&#039;Your aws account&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;Policy&#039;&#039;&#039; now needs to be created for the role to use, lets use this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
     &amp;quot;Version&amp;quot;: &amp;quot;2012-10-17&amp;quot;, &lt;br /&gt;
     &amp;quot;Statement&amp;quot;: [ &lt;br /&gt;
      { &lt;br /&gt;
        &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3PutPolicy&amp;quot;,&amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
        &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
          &amp;quot;s3:PutObject&amp;quot;, &lt;br /&gt;
          &amp;quot;s3:PutObjectAcl&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;:[ &lt;br /&gt;
         &amp;quot;arn:aws:s3:::packt-config/*&amp;quot; &lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Condition&amp;quot;:{ &lt;br /&gt;
         &amp;quot;StringLike&amp;quot;:{ &lt;br /&gt;
           &amp;quot;s3:x-amz-acl&amp;quot;:&amp;quot;bucket-owner-full-control&amp;quot; &lt;br /&gt;
         } &lt;br /&gt;
       } &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigS3GetPolicy&amp;quot;,&lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &amp;quot;s3:GetBucketAcl&amp;quot; ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:aws:s3::&#039;&#039;&#039;s3 bucket&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;ConfigSNSPolicy&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;: &amp;quot;sns:Publish&amp;quot;, &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;arn:&#039;&#039;&#039;SNS-ARN&#039;&#039;&#039;&amp;quot; &lt;br /&gt;
      }, &lt;br /&gt;
      { &lt;br /&gt;
       &amp;quot;Sid&amp;quot;: &amp;quot;DescribeResources&amp;quot;, &lt;br /&gt;
       &amp;quot;Effect&amp;quot;: &amp;quot;Allow&amp;quot;, &lt;br /&gt;
       &amp;quot;Action&amp;quot;:[ &lt;br /&gt;
         &amp;quot;ec2:Describe*&amp;quot;&lt;br /&gt;
       ], &lt;br /&gt;
       &amp;quot;Resource&amp;quot;: &amp;quot;*&amp;quot; &lt;br /&gt;
      } &lt;br /&gt;
    ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Let&#039;s break the JSON down for understanding:&lt;br /&gt;
&lt;br /&gt;
:* It provides access to the bucket to write objects&lt;br /&gt;
&lt;br /&gt;
:* It provides assess to SNS for push data&lt;br /&gt;
&lt;br /&gt;
:* It allows allows the discerption of ec2 resources &lt;br /&gt;
&lt;br /&gt;
The entire process is captured:&lt;br /&gt;
&lt;br /&gt;
: Describe &amp;gt; Transmit (SNS) &amp;gt; Save (s3)&lt;br /&gt;
&lt;br /&gt;
With this done we can attach the policy to the role:&lt;br /&gt;
&lt;br /&gt;
This can be done in the AWS CLI with the following command:&lt;br /&gt;
&lt;br /&gt;
 aws iam attach-role-policy --role-name &#039;&#039;&#039;role name&#039;&#039;&#039; --policy-arn &#039;&#039;&#039;policy arn&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next and very importantly we need to determine what resources to capture.&lt;br /&gt;
&lt;br /&gt;
:* Keep in mind you will pay a nominal free for these / but this is AWS - resources add up $$$&lt;br /&gt;
&lt;br /&gt;
:* If you monitor too little you won&#039;t get the data you need to make decisions or protect the system.&lt;br /&gt;
&lt;br /&gt;
:* Decide what is right for your system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of the JSON file:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 { &lt;br /&gt;
           &amp;quot;allSupported&amp;quot;: false, &lt;br /&gt;
           &amp;quot;includeGlobalResourceTypes&amp;quot;: false, &lt;br /&gt;
           &amp;quot;resourceTypes&amp;quot;: [ &lt;br /&gt;
                   &amp;quot;AWS::EC2::SecurityGroup&amp;quot;, &lt;br /&gt;
                   &amp;quot;AWS::EC2::Volume&amp;quot; &lt;br /&gt;
           ] &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will monitor:&lt;br /&gt;
&lt;br /&gt;
::* EC2 security groups.&lt;br /&gt;
&lt;br /&gt;
::* EC2 Volue status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next create a delivery file:&lt;br /&gt;
&lt;br /&gt;
{ &lt;br /&gt;
           &amp;quot;name&amp;quot;: &amp;quot;default&amp;quot;, &lt;br /&gt;
           &amp;quot;s3BucketName&amp;quot;: &amp;quot;&#039;&#039;your-bucket&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;snsTopicARN&amp;quot;: &amp;quot;arn:aws:sns:&#039;&#039;your-sns&#039;&#039;&amp;quot;, &lt;br /&gt;
           &amp;quot;configSnapshotDeliveryProperties&amp;quot;: { &lt;br /&gt;
               &amp;quot;deliveryFrequency&amp;quot;: &amp;quot;Twelve_Hours&amp;quot; &lt;br /&gt;
           } &lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Breaking it down:&lt;br /&gt;
&lt;br /&gt;
::* Connects the S3 bucket&lt;br /&gt;
&lt;br /&gt;
::* Connects the SNS&lt;br /&gt;
&lt;br /&gt;
::* Defines the frequency&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, start the recorder&lt;br /&gt;
&lt;br /&gt;
 aws configservice start-configuration-recorder --configuration-recorder-name &#039;&#039;name&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::* It will take a few minutes for the data to be posted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AWS Config Rules =&lt;br /&gt;
&lt;br /&gt;
Rules enable you to automatically evaluate the configuration of monitored resources.&lt;br /&gt;
&lt;br /&gt;
A rule can be triggered in two ways:&lt;br /&gt;
&lt;br /&gt;
:* When a resource changes&lt;br /&gt;
&lt;br /&gt;
:* On a schedule&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These rules allow you to enfore a consistant approach to AWS resources.&lt;br /&gt;
&lt;br /&gt;
: This is independent of who deployed them or when they where deployed.&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1604</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1604"/>
		<updated>2026-05-19T17:25:12Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
=== Do no harm ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;👉Breaking these will get you a lifetime ban&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Help each other on our journey ===&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== We are here... for all mankind ===&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Keep your author account in good standing ===&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1603</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1603"/>
		<updated>2026-05-19T17:24:23Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Cramsession Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
=== Do no harm ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;👉Breaking these will get you a lifetime ban&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Help each other on our journey ===&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== We are here... for all mankind ===&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Keep your author account in good standing ===&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1602</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1602"/>
		<updated>2026-05-19T17:22:59Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Cramsession Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
=== Do no harm ===&lt;br /&gt;
&lt;br /&gt;
Breaking these will get you a lifetime ban&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Help each other on our journey ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Lets play nice kids&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== We are here... for all mankind ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Help the universe&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Keep your author account in good standing ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Just the right thing to do&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1601</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1601"/>
		<updated>2026-05-19T17:21:49Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Cramsession Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
* Do no harm&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Breaking these will get you a lifetime ban&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar, main landing page or these rules.&lt;br /&gt;
&lt;br /&gt;
:* Be polite!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help each other on our journey&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Lets play nice kids&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* We are here... for all mankind.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Help the universe&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Keep your author account in good standing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Just the right thing to do&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1600</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1600"/>
		<updated>2026-05-19T17:16:53Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Protected &amp;quot;Rules&amp;quot; ([Edit=Allow only administrators] (indefinite))&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
* Do no harm&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar or main landing page - all other pages are editable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help each other on our journey&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* We are here... for all mankind.&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Keep your author account in good standing.&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1599</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1599"/>
		<updated>2026-05-19T17:15:00Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: /* Contacting us */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
* Do no harm&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar or main landing page - all other pages are editable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help each other on our journey&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* We are here... for all mankind.&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Keep your author account in good standing.&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;br /&gt;
&lt;br /&gt;
Reach out via email: info@907technology.com&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=Rules&amp;diff=1598</id>
		<title>Rules</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=Rules&amp;diff=1598"/>
		<updated>2026-05-19T17:13:43Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: Created page with &amp;quot; = Introduction =  Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.  == Cramsession Code ==  * Do no harm  :* Don&amp;#039;t post hate / sex , engage in hateful or illegal activity on this site.  :* Don&amp;#039;t deface the pages created by other authors.  :* Don&amp;#039;t attempt to edit the sidebar or main landing page - all other pages are editable.   * Help each other on our j...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
Cramsession was found on the principle of providing validated, clean content to the internet community. As part of this core mission authors must follow these rules.&lt;br /&gt;
&lt;br /&gt;
== Cramsession Code ==&lt;br /&gt;
&lt;br /&gt;
* Do no harm&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t post hate / sex , engage in hateful or illegal activity on this site.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t deface the pages created by other authors.&lt;br /&gt;
&lt;br /&gt;
:* Don&#039;t attempt to edit the sidebar or main landing page - all other pages are editable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help each other on our journey&lt;br /&gt;
&lt;br /&gt;
:* If you see incorrect information, help the author correct it by editing the page directly.&lt;br /&gt;
&lt;br /&gt;
:* if you think a page needs more content, add it - this is our community.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* We are here... for all mankind.&lt;br /&gt;
&lt;br /&gt;
:* You do not own the information you post on this site, even if your account is deleted your content will stay online forever.&lt;br /&gt;
&lt;br /&gt;
:* If you have any problems, communicate with us.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Keep your author account in good standing.&lt;br /&gt;
&lt;br /&gt;
:* The $10 (USD) a month will be debited automatically (we need to pay our humans, and the bills)&lt;br /&gt;
&lt;br /&gt;
:* Keep your certifications in good standing - let us know if you get anything new.&lt;br /&gt;
&lt;br /&gt;
== Contacting us ==&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
	<entry>
		<id>https://cramsession.net/index.php?title=MediaWiki:Sidebar&amp;diff=1597</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://cramsession.net/index.php?title=MediaWiki:Sidebar&amp;diff=1597"/>
		<updated>2026-05-19T16:56:58Z</updated>

		<summary type="html">&lt;p&gt;Mflavell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;** Computer Notes|📝Computer Notes&lt;br /&gt;
&lt;br /&gt;
** Study Guides|📕Study Guides&lt;br /&gt;
&lt;br /&gt;
** Cybersecurity | 🪲Cybersecurity&lt;br /&gt;
&lt;br /&gt;
** Radio | 📻Radio Notes&lt;br /&gt;
&lt;br /&gt;
** APA Guide | 🧑‍🎓APA Guide&lt;br /&gt;
&lt;br /&gt;
** Theory | 🤔Theory&lt;br /&gt;
&lt;br /&gt;
** Rules | 🚓 Rules&lt;br /&gt;
&lt;br /&gt;
** Cramsession:About | ❓About us&lt;/div&gt;</summary>
		<author><name>Mflavell</name></author>
	</entry>
</feed>