Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

README.md

sumologic-securityhub-forwarder

This lambda function is used for importing findings from Sumo Logic to AWS Security Hub.

Made with ❤️ by Sumo Logic. Available on the AWS Serverless Application Repository

Sumo to Security Hub Collection Flow

Setup

  1. Enable Sumo Logic as a finding provider. Refer the docs

  2. Deploying the SAM Application

    1. Go to https://serverlessrepo.aws.amazon.com/applications.
    2. Search for sumologic-securityhub-forwarder.
    3. Click on Deploy
    4. Copy the value of SecurityHubForwarderApiUrl from Output which is the API Gateway endpoint.
  3. Create a Webhook connection.Use the value copied in step 1.4 as URL. Note: SAM application already secures the endpoint with AWS_IAM authorization type It should have the following payload

     "Types": "<type> Ex: Software and Configuration Checks/Industry and Regulatory Standards/PCI-DSS Controls",
     "Description": "{{SearchDescription}}",
     "SourceUrl": "{{SearchQueryUrl}}",
     "GeneratorID": "{{SearchName}}",
     "Severity": <number from 0 to 100>,
     "Rows": "{{AggregateResultsJson}}",
     "ComplianceStatus": "(Optional)<status> - PASSED/WARNING/FAILED/NOT_AVAILABLE"
  }

Also make sure the IAM role or IAM user(whose credentials are used) has permissions to invoke the api in API Gateway. Refer the docs

  1. Create scheduled searches, as described in this document, and configure the following settings:

    • Alert condition is set to “Greater than >” and Number of Results is set to 0.
    • Alert Type is set to “Webhook”.
    • Connection is set to the name configured in step 2 (of the link document instructions).
    • Toggle the customize payload button and fill the fields in the following dialog. The following table explains each field.
    Field Description
    Types Type of Finding in the format namespace/category/classifier.This field should match one of the finding types, as defined in Finding Type Taxonomy in AWS docs.
    Description Details specific to the instance of the finding.This should be non empty.
    SourceURL Search Query URL pointing to the exact query that generated the finding.
    GeneratorID Scheduled Search Name that generated this finding.
    Severity Impact of a finding has on a customer (data loss, malware activity, configuration weakness etc), displayed as an integer ranging from 0 to 100.
    ComplianceStatus Results of a compliance check. This is an optional field and its value should be one of the following: PASSED/WARNING/FAILED/NOT_AVAILABLE.

Also the rows in AggregateResultsJson should contain following mandatory fields "finding_time"(timestamp), "resource_type", "resource_id", "title"

“aws_account_id” is optional field in search results. Lambda function will pick up it’s value in following order search results(each row) > aws_account_id environment variable > defaults to the account in which lambda is running

License

Apache License 2.0 (Apache-2.0)

Support

Requests & issues should be filed on GitHub: https://github.com/SumoLogic/sumologic-aws-lambda/issues