AWS solutions documentation change
Summary
Replaced 'solution' with 'Guidance' in multiple instances and updated terminology from 'Forensic Solution' to 'Forensic Guidance'
Security assessment
Changes appear to be terminology updates rather than security-related modifications. The updates focus on branding/naming conventions without introducing new security controls or addressing vulnerabilities.
Diff
diff --git a/solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/steps-to-build-volatility-profile-using-ssm-document.md b/solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/steps-to-build-volatility-profile-using-ssm-document.md index 89c39f8b0..2db9f469d 100644 --- a//solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/steps-to-build-volatility-profile-using-ssm-document.md +++ b//solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/steps-to-build-volatility-profile-using-ssm-document.md @@ -40 +40 @@ Currently the profile and tools are loaded into the S3 bucket for Amazon Linux E -You can incorporate the module build process for LiME and Volatility (or your preferred forensic tools) into a hardened AMI pipeline prior to allowing AMI use by developers and application teams. These modules are prerequisites for running the Automated Forensics Orchestrator for Amazon EC2 solution to allow the capture and analysis of volatile memory. You also need to incorporate a mechanism to build these modules for the specific kernel versions in the event they do not exist. This can occur if an EC2 instance is updated after being launched or if an EC2 instance was launched from a non-hardened AMI that is not managed by a central team. +You can incorporate the module build process for LiME and Volatility (or your preferred forensic tools) into a hardened AMI pipeline prior to allowing AMI use by developers and application teams. These modules are prerequisites for running the Automated Forensics Orchestrator for Amazon EC2 Guidance to allow the capture and analysis of volatile memory. You also need to incorporate a mechanism to build these modules for the specific kernel versions in the event they do not exist. This can occur if an EC2 instance is updated after being launched or if an EC2 instance was launched from a non-hardened AMI that is not managed by a central team. @@ -42 +42 @@ You can incorporate the module build process for LiME and Volatility (or your pr -For more information, refer to the [How to automatically build forensic kernel modules for Amazon Linux EC2 instances](https://aws.amazon.com/blogs/security/how-to-automatically-build-forensic-kernel-modules-for-amazon-linux-ec2-instances/) blog, which will walk you through deploying a solution to automatically build modules for specific EC2 instance OS kernel versions based on input parameters of AMI ID and kernel version. You can use the blog solution with the Automated Forensics Orchestrator for Amazon EC2 solution in the event that specific kernel module versions are missing and need to be created. +For more information, refer to the [How to automatically build forensic kernel modules for Amazon Linux EC2 instances](https://aws.amazon.com/blogs/security/how-to-automatically-build-forensic-kernel-modules-for-amazon-linux-ec2-instances/) blog, which will walk you through deploying a Guidance to automatically build modules for specific EC2 instance OS kernel versions based on input parameters of AMI ID and kernel version. You can use the blog Guidance with the Automated Forensics Orchestrator for Amazon EC2 Guidance in the event that specific kernel module versions are missing and need to be created. @@ -52 +52 @@ Post deployment: Plugin points -Usage of Forensic Solution +Usage of Forensic Guidance