This blog post is the first of a two-part series that will demonstrate the value of Amazon Security Lake and how you can use it and other resources to accelerate your incident response (IR) capabilities. Security Lake is a purpose-built data lake that centrally stores your security logs in a common, industry-standard format. In part one, we will first demonstrate the value Security Lake can bring at each stage of the National Institute of Standards and Technology (NIST) SP 800-61 Computer Security Incident Handling Guide. We will then demonstrate how you can configure Security Lake in a multi-account deployment by using the AWS Security Reference Architecture (AWS SRA).

   <p>In part two of this series, we’ll walk through an example to show you how to use Security Lake and other AWS services and tools to drive an incident to resolution.</p> 
   <p>At <a href="https://aws.amazon.com/" target="_blank" rel="noopener">Amazon Web Services (AWS)</a>, security is our top priority. When security incidents occur, customers need the right capabilities to quickly investigate and resolve them. Security Lake enhances your capabilities, especially during the detection and analysis stages, which can reduce time to resolution and business impact. We also cover <a href="https://docs.aws.amazon.com/wellarchitected/latest/framework/a-incident-response.html" target="_blank" rel="noopener">incident response</a> specifically in the security pillar of the <a href="https://aws.amazon.com/architecture/well-architected/" target="_blank" rel="noopener">AWS Well-Architected Framework</a>, provide <a href="https://docs.aws.amazon.com/whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.html" target="_blank" rel="noopener">prescriptive guidance on preparing for and handling incidents</a>, and publish <a href="https://github.com/aws-samples/aws-incident-response-playbooks" target="_blank" rel="noopener">incident response playbooks</a>.</p> 
   <h2>Incident response life cycle</h2> 
   <p><a href="https://www.nist.gov/privacy-framework/nist-sp-800-61" target="_blank" rel="noopener">NIST SP 800-61</a> describes a set of steps you use to resolve an incident. These include preparation (Stage 1), detection and analysis (Stage 2), containment, eradication and recovery (Stage 3), and finally post-incident activities (Stage 4).</p> 
   <p>Figure 1 shows the workflow of incident response defined by NIST SP 800-61. The response flows from Stage 1 through Stage 4, with Stages 2 and 3 often being an iterative process. We will discuss the value of <a href="https://aws.amazon.com/security-lake/" target="_blank" rel="noopener">Security Lake</a> at each stage of the NIST incident response handling process, with a focus on preparation, detection, and analysis.</p> 
   <div id="attachment_34360" class="wp-caption aligncenter"> 
    <img aria-describedby="caption-attachment-34360" src="https://infracom.com.sg/wp-content/uploads/2024/05/img1_v2-1.png" alt="Figure 1: NIST 800-61 incident response life cycle. Source: NIST 800-61" width="780" class="size-full wp-image-34360"> 
    <p id="caption-attachment-34360" class="wp-caption-text">Figure 1: NIST 800-61 incident response life cycle. Source: NIST 800-61</p> 
   </div> 
   <h3>Stage 1: Preparation</h3> 
   <p>Preparation helps you ensure that tools, processes, and people are prepared for incident response. In some cases, preparation can also help you identify systems, networks, and applications that might not be sufficiently secure. For example, you might determine you need certain system logs for incident response, but discover during preparation that those logs are not enabled.</p> 
   <p>Figure 2 shows how Security Lake can accelerate the preparation stage during the incident response process. Through native integration with various security data sources from both AWS services and third-party tools, Security Lake simplifies the integration and concentration of security data, which also facilitates training and rehearsal for incident response.</p> 
   <div id="attachment_34351" class="wp-caption aligncenter"> 
    <img aria-describedby="caption-attachment-34351" src="https://infracom.com.sg/wp-content/uploads/2024/05/img2-9.png" alt="Figure 2: Amazon Security Lake data consolidation for IR preparation" width="780" class="size-full wp-image-34351"> 
    <p id="caption-attachment-34351" class="wp-caption-text">Figure 2: Amazon Security Lake data consolidation for IR preparation</p> 
   </div> 
   <p>Some challenges in the preparation stage include the following:</p> 
   <ul> 
    <li><strong>Insufficient incident response planning, training, and rehearsal –</strong> Time constraints or insufficient resources can slow down preparation.</li> 
    <li><strong>Complexity of system integration and data sources –</strong> An increasing number of security data sources and integration points require additional integration effort, or increase risk that some log sources are not integrated.</li> 
    <li><strong>Centralized log repository for mixed environments –</strong> Customers with both on-premises and cloud infrastructure told us that consolidating logs for those mixed environments was a challenge.</li> 
   </ul> 
   <p>Security Lake can help you deal with these challenges in the following ways:</p> 
   <ul> 
    <li><strong>Simplify system integration with security data normalization</strong> 
      </li> 
    <li><strong>Streamline data consolidation across mixed environments</strong> 
     <ul> 
      <li>Security Lake supports multiple log sources, including <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/internal-sources.html" target="_blank" rel="noopener">AWS native services</a> and <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/custom-sources.html" target="_blank" rel="noopener">custom sources</a>, which include third-party partner solutions, other cloud platforms and your on-premises log sources. For example, see <a href="https://aws.amazon.com/blogs/security/get-custom-data-into-amazon-security-lake-through-ingesting-azure-activity-logs/" target="_blank" rel="noopener">this blog post</a> to learn how to ingest Microsoft Azure activity logs into Security Lake.</li> 
     </ul> </li> 
    <li><strong>Facilitate IR planning and testing</strong> 
     <ul> 
      <li>Security Lake reduces the undifferentiated heavy lifting needed to get security data into tooling so teams spend less time on configuration and data extract, transform, and load (ETL) work and more time on preparedness.</li> 
      <li>With a purpose-built security data lake and data retention policies that you define, security teams can integrate data-driven decision making into their planning and testing, answering questions such as “which incident handling capabilities do we prioritize?” and running <a href="https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.gameday.en.html" target="_blank" rel="noopener">Well-Architected game days</a>.</li> 
     </ul> </li> 
   </ul> 
   <h3>Stages 2 and 3: Detection and Analysis, Containment, Eradication and Recovery</h3> 
   <p>The Detection and Analysis stage (Stage 2) should lead you to understand the immediate cause of the incident and what steps need to be taken to contain it. Once contained, it’s critical to fully eradicate the issue. These steps form Stage 3 of the incident response cycle. You want to ensure that those malicious artifacts or exploits are removed from systems and verify that the impacted service has recovered from the incident.</p> 
   <p>Figure 3 shows how Security Lake can enable effective detection and analysis. Doing so enables teams to quickly contain, eradicate, and recover from the incident. Security Lake natively integrates with other AWS analytics services, such as <a href="https://aws.amazon.com/athena/" target="_blank" rel="noopener">Amazon Athena</a>, <a href="https://aws.amazon.com/quicksight/" target="_blank" rel="noopener">Amazon QuickSight</a>, and <a href="https://aws.amazon.com/opensearch-service/" target="_blank" rel="noopener">Amazon OpenSearch Service</a>, which makes it easier for your security team to generate insights on the nature of the incident and to take relevant remediation steps.</p> 
   <div id="attachment_34352" class="wp-caption aligncenter"> 
    <img aria-describedby="caption-attachment-34352" src="https://infracom.com.sg/wp-content/uploads/2024/05/img3-9.png" alt="Figure 3: Amazon Security Lake accelerates IR Detection and Analysis, Containment, Eradication, and Recovery" width="780" class="size-full wp-image-34352"> 
    <p id="caption-attachment-34352" class="wp-caption-text">Figure 3: Amazon Security Lake accelerates IR Detection and Analysis, Containment, Eradication, and Recovery</p> 
   </div> 
   <p>Common challenges present in stages 2 and 3 include the following:</p> 
   <ul> 
    <li><strong>Challenges generating insights from disparate data sources</strong> 
     <ul> 
      <li>Inability to generate insights from security data means teams are less likely to discover an incident, as opposed to having the breach revealed to them by a third party (such as a threat actor).</li> 
      <li>Breaches disclosed by a threat actor might involve higher costs than incidents discovered by the impacted organizations themselves, because typically the unintended access has progressed for longer and impacted more resources and data than if the impacted organization discovered it sooner.</li> 
     </ul> </li> 
    <li><strong>Inconsistency of data visibility and data siloing</strong> 
     <ul> 
      <li>Security log data silos may slow IR data analysis because it’s challenging to gather and correlate the necessary information to understand the full scope and impact of an incident. This can lead to delays in identifying the root cause, assessing the damage, and taking remediation steps.</li> 
      <li>Data silos might also mean additional permissions management overhead for administrators.</li> 
     </ul> </li> 
    <li><strong>Disparate data sources add barriers to adopting new technology, such as AI-driven security analytics tools</strong> 
     <ul> 
      <li>AI-driven security analysis requires a large amount of security data from various data sources, which might be in disparate formats. Without a centralized security data repository, you might need to make additional effort to ingest and normalize data for model training.</li> 
     </ul> </li> 
   </ul> 
   <p>Security Lake offers native support for log ingestion for a range of AWS security services, including <a href="https://aws.amazon.com/cloudtrail/" target="_blank" rel="noopener">AWS CloudTrail</a>, <a href="https://aws.amazon.com/security-hub/" target="_blank" rel="noopener">AWS Security Hub</a>, and <a href="https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html" target="_blank" rel="noopener">VPC Flow Logs</a>. Additionally, you can configure Security Lake to ingest external sources. This helps enrich findings and alerts.</p> 
   <p>Security Lake addresses the preceding challenges as follows:</p> 
   <ul> 
    <li><strong>Unleash security detection capability by centralizing detection data</strong> 
     <ul> 
      <li>With a purpose-built security data lake with a standard object schema, organizations can centrally access their security data—AWS and third-party—using the same set of IR tools. This can help you investigate incidents that involve multiple resources and complex timelines, which could require access logs, network logs, and other security findings. For example, use <a href="https://aws.amazon.com/athena/" target="_blank" rel="noopener">Amazon Athena</a> to query all your security data. You can also build a <a href="https://aws.amazon.com/blogs/security/how-to-visualize-amazon-security-lake-findings-with-amazon-quicksight/" target="_blank" rel="noopener">centralized security finding dashboard with Amazon QuickSight</a>.</li> 
     </ul> </li> 
    <li><strong>Reduce management burden</strong> 
     <ul> 
      <li>With Security Lake, permissions complexity is reduced. You use the same access controls in <a href="https://aws.amazon.com/iam/" target="_blank" rel="noopener">AWS Identity and Access Management (IAM)</a> to make sure that only the right people and systems have access to sensitive security data.</li> 
     </ul> </li> 
   </ul> 
   <p>See <a href="https://aws.amazon.com/blogs/security/generate-machine-learning-insights-for-amazon-security-lake-data-using-amazon-sagemaker/" target="_blank" rel="noopener">this blog post</a> for more details on generating machine learning insights for Security Lake data by using <a href="https://aws.amazon.com/pm/sagemaker" target="_blank" rel="noopener">Amazon SageMaker</a>.</p> 
   <h3>Stage 4: Post-Incident Activity</h3> 
   <p>Continuous improvement helps customers to further develop their IR capabilities. Teams should integrate lessons learned into their tools, policies, and processes. You decide on <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/lifecycle-management.html" target="_blank" rel="noopener">lifecycle policies for your security data</a>. You can then retroactively review event data for insight and to support lessons learned. You can also <a href="https://aws.amazon.com/blogs/security/how-to-share-security-telemetry-per-ou-using-amazon-security-lake-and-aws-lake-formation/" target="_blank" rel="noopener">share security telemetry</a> at levels of granularity you define. Your organization can then establish distributed data views for forensic purposes and other purposes, while enforcing least privilege for data governance.</p> 
   <p>Figure 4 shows how Security Lake can accelerate the post-incident activity stage during the incident response process. Security Lake natively integrates with <a href="https://aws.amazon.com/organizations/" target="_blank" rel="noopener">AWS Organizations</a> to enable data sharing across various OUs within the organization, which further unleashes the power of machine learning to automatically create insights for incident response.</p> 
   <div id="attachment_34353" class="wp-caption aligncenter"> 
    <img aria-describedby="caption-attachment-34353" src="https://infracom.com.sg/wp-content/uploads/2024/05/img4-9.png" alt="Figure 4: Security Lake accelerates post-incident activity" width="780" class="size-full wp-image-34353"> 
    <p id="caption-attachment-34353" class="wp-caption-text">Figure 4: Security Lake accelerates post-incident activity</p> 
   </div> 
   <p>Having covered some advantages of working with your data in Security Lake, we will now demonstrate best practices for getting Security Lake set up.</p> 
   <h2>Setting up for success with Security Lake</h2> 
   <p>Most of the customers we work with run multiple AWS accounts, usually with <a href="https://aws.amazon.com/organizations/" target="_blank" rel="noopener">AWS Organizations</a>. With that in mind, we’re going to show you how to set up Security Lake and related tooling in line with guidance in the <a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/security-reference-architecture/welcome.html" target="_blank" rel="noopener">AWS Security Reference Architecture (AWS SRA)</a>. The AWS SRA provides guidance on how to deploy AWS security services in a multi-account environment. You will have one AWS account for security tooling and a different account to centralize log storage. You’ll run Security Lake in this log storage account.</p> 
   <p>If you just want to use Security Lake in a standalone account, follow <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/getting-started.html" target="_blank" rel="noopener">these instructions</a>.</p> 
   <h3>Set up Security Lake in your logging account</h3> 
   <p>Most of the instructions we link to in this section describe the process using either the console or AWS CLI tools. Where necessary, we’ve described the console experience for illustrative purposes.</p> 
   <p>The <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonSecurityLakeAdministrator" target="_blank" rel="noopener">AmazonSecurityLakeAdministrator</a> AWS managed IAM policy grants the permissions needed to set up Security Lake and related services. Note that you may want to further refine permissions, or remove that managed policy after Security Lake and the related services are set up and running.</p> 
   <h4>To set up Security Lake in your logging account</h4> 
   <ol> 
    <li>Note down the AWS account number that will be your <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/multi-account-management.html#designated-admin" target="_blank" rel="noopener">delegated administrator account</a>. This will be your centralized archive logs account. In the AWS Management Console, sign in to your Organizations management account and set up delegated administration for Security Lake.</li> 
    <li>Sign in to the delegated administrator account, go to the Security Lake console, and choose <strong>Get started</strong>. Then follow <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/getting-started.html#get-started-console" target="_blank" rel="noopener">these instructions from the Security Lake User Guide</a>. While you’re setting this up, note the following specific guidance (this will make it easier to follow the second blog post in this series): <p><strong>Define source objective:</strong> For <strong>Sources to ingest</strong>, we recommend that you select <strong>Ingest the AWS default sources</strong>. However, if you want to include S3 data events, you’ll need to select <strong>Ingest specific AWS sources</strong> and then select <strong>CloudTrail – S3 data events</strong>. Note that we use these events for responding to the incident in blog post part 2, when we really drill down into user activity.</p> <p>Figure 5 shows the configuration of sources to ingest in Security Lake.</p> 
     <div id="attachment_34354" class="wp-caption aligncenter"> 
      <img aria-describedby="caption-attachment-34354" src="https://infracom.com.sg/wp-content/uploads/2024/05/img5-6.png" alt="Figure 5: Sources to ingest in Security Lake" width="740" class="size-full wp-image-34354"> 
      <p id="caption-attachment-34354" class="wp-caption-text">Figure 5: Sources to ingest in Security Lake</p> 
     </div> <p>We recommend leaving the other settings on this page as they are.</p> <p><strong>Define target objective</strong>: We recommend that you choose <strong>Add rollup Region</strong> and add multiple AWS Regions to a designated rollup Region. The rollup Region is the one to which you will consolidate logs. The contributing Region is the one that will contribute logs to the rollup Region.</p> <p>Figure 6 shows how to select the rollup regions.</p> 
     <div id="attachment_34355" class="wp-caption aligncenter"> 
      <img aria-describedby="caption-attachment-34355" src="https://infracom.com.sg/wp-content/uploads/2024/05/img6-5.png" alt="Figure 6: Select rollup Regions" width="740" class="size-full wp-image-34355"> 
      <p id="caption-attachment-34355" class="wp-caption-text">Figure 6: Select rollup Regions</p> 
     </div> </li> 
   </ol> 
   <p>You now have Security Lake enabled, and in the background, additional services such as <a href="https://aws.amazon.com/lake-formation/" target="_blank" rel="noopener">AWS Lake Formation</a> and <a href="https://aws.amazon.com/glue/" target="_blank" rel="noopener">AWS Glue</a> have been configured to organize your Security Lake data.</p> 
   <p>Now you need to <a href="https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-query-access.html" target="_blank" rel="noopener">configure a subscriber with query access</a> so that you can query your Security Lake data. Here are a few recommendations:</p> 
   <ol> 
    <li>Subscribers are specific to a Region, so you want to make sure that you set up your subscriber in the same Region as your rollup Region.</li> 
    <li>You will also set up an External ID. This is a value you define, and it’s used by the IAM role to prevent the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html" target="_blank" rel="noopener">confused deputy problem</a>. Note that the subscriber will be your security tooling account.</li> 
    <li>You will select <strong>Lake Formation</strong> for <strong>Data access</strong>, which will create shares in <a href="https://aws.amazon.com/ram/" target="_blank" rel="noopener">AWS Resource Access Manager (AWS RAM)</a> that will be shared with the account that you specified in <strong>Subscriber credentials</strong>.</li> 
    <li>If you’ve already set up Security Lake at some time in the past, you should select <strong>Specific log and event sources</strong> and confirm the source and version you want the subscriber to access. If it’s a new implementation, we recommend using version 2.0 or greater.</li> 
    <li>There’s a note in the console that says the subscribing account will need to accept the RAM resource shares. However, if you’re using AWS Organizations, you don’t need to do that; the resource share will already list a status of <strong>Active</strong> when you select the <strong>Shared with me &gt;&gt; Resource shares</strong> in the subscriber (security tooling) account RAM console.</li> 
   </ol> 
   <blockquote> 
    <p><strong>Note:</strong> If you prefer a visual guide, you can refer to <a href="https://www.youtube.com/watch?v=fKGhscpwN-k" target="_blank" rel="noopener">this video</a> to set up Security Lake in AWS Organizations.</p> 
   </blockquote> 
   <h3>Set up Amazon Athena and AWS Lake Formation in the security tooling account</h3> 
   <p>If you go to Athena in your security tooling account, you won’t see your Security Lake tables yet because the tables are shared from the Security Lake account. Although <a href="https://docs.aws.amazon.com/lake-formation/latest/dg/resource-links-about.html" target="_blank" rel="noopener">services such as Amazon Athena can’t directly access databases or tables across accounts</a>, the use of resource links overcomes this challenge.</p> 
   <h4>To set up Athena and Lake Formation</h4> 
   <ol> 
    <li>Go to the Lake Formation console in the security tooling account and follow the <a href="https://docs.aws.amazon.com/lake-formation/latest/dg/create-resource-link-table.html" target="_blank" rel="noopener">instructions to create resource links for the shared Security Lake tables</a>. You’ll most likely use the <strong>Default</strong> database and will see your tables there. The table names in that database start with <span>amazon_security_lake_table</span>. You should expect to see about eight tables there. <p>Figure 7 shows the shared tables in the Lake Formation service console.</p> 
     <div id="attachment_34356" class="wp-caption aligncenter"> 
      <img aria-describedby="caption-attachment-34356" src="https://infracom.com.sg/wp-content/uploads/2024/05/img7-5.png" alt="Figure 7: Shared tables in Lake Formation" width="740" class="size-full wp-image-34356"> 
      <p id="caption-attachment-34356" class="wp-caption-text">Figure 7: Shared tables in Lake Formation</p> 
     </div> <p>You will need to create resource links for each table, as described in the instructions from the Lake Formation Developer Guide.</p> <p>Figure 8 shows the resource link creation process.</p> 
     <div id="attachment_34357" class="wp-caption aligncenter"> 
      <img aria-describedby="caption-attachment-34357" src="https://infracom.com.sg/wp-content/uploads/2024/05/img8-4.png" alt="Figure 8: Creating resource links" width="740" class="size-full wp-image-34357"> 
      <p id="caption-attachment-34357" class="wp-caption-text">Figure 8: Creating resource links</p> 
     </div> </li> 
    <li>Next, go to Amazon Athena in the same Region. If Athena is not set up, <a href="https://docs.aws.amazon.com/athena/latest/ug/getting-started.html" target="_blank" rel="noopener">follow the instructions to get it set up for SQL queries</a>. Note that you won’t need to create a database—you’re going to use the “default” database that already exists. Select it from the <strong>Database</strong> drop-down menu in the <strong>Query editor</strong> view.</li> 
    <li>In the <strong>Tables</strong> section, you should see all your Security Lake tables (represented by whatever names you gave them when you created the resource links in step 1, earlier).</li> 
   </ol> 
   <h3>Get your incident response playbooks ready</h3> 
   <p>Incident response playbooks are an important tool that enable responders to work more effectively and consistently, and enable the organization to get incidents resolved more quickly. We’ve created some <a href="https://github.com/aws-samples/aws-incident-response-playbooks" target="_blank" rel="noopener">ready-to-go templates</a> to get you started. You can further customize these templates to meet your needs. In part two of this post, you’ll be using the <a href="https://github.com/aws-samples/aws-incident-response-playbooks/blob/master/playbooks/IRP-DataAccess.md" target="_blank" rel="noopener">Unintended Data Access to an Amazon Simple Storage Service (Amazon S3) bucket</a> playbook to resolve an incident. You can download that playbook so that you’re ready to follow it to get that incident resolved.</p> 
   <h2>Conclusion</h2> 
   <p>This is the first post in a two-part series about accelerating security incident response with Security Lake. We highlighted common challenges that decelerate customers’ incident responses across the stages outlined by NIST SP 800-61 and how Security Lake can help you address those challenges. We also showed you how to set up Security Lake and related services for incident response.</p> 
   <p>In the second part of this series, we’ll walk through a specific security incident—unintended data access—and share prescriptive guidance on using Security Lake to accelerate your incident response process.</p> 
   <p> <br>If you have feedback about this post, submit comments in the<strong> Comments</strong> section below. If you have questions about this post, <a href="https://console.aws.amazon.com/support/home" target="_blank" rel="noopener noreferrer">contact AWS Support</a>.</p> 
   <p><strong>Want more AWS Security news? Follow us on <a title="Twitter" href="https://twitter.com/AWSsecurityinfo" target="_blank" rel="noopener noreferrer">Twitter</a>.</strong></p> 

   <!-- '"` -->