Skip to content

Azure Sentinel Data connector to collect AWS GuardDuty Findings from AWS S3

License

Notifications You must be signed in to change notification settings

andedevsecops/AzSentinel-AWSGuardDuty

Repository files navigation

Azure Sentinel Data connector to ingest AWS GuardDuty Findings

Azure Sentinel Data connector to ingest AWS GuardDuty Findings

Function Flow process

GuardDuty Findings --> AWS S3 --> Azure Function --> Azure Log Analytics

Installation / Setup Guide

  1. Click "Deploy To Azure" (For both Commercial & Azure GOV)
  1. Select the preferred Subscription, Resource Group and Location
    Note
    Best practice : Create new Resource Group while deploying - all the resources of your custom Data connector will reside in the newly created Resource Group
  2. Enter the following value in the ARM template deployment
    "Workspace Id": Azure Log Analytics Workspace Id​
    "Workspace Key": Azure Log Analytics Workspace Key
    "AWS Access Key Id": AWS Access Key
    "AWS Secret Key ID": AWS Secret Key
    "AWS Region Name" : AWS SecurityHub Region
    "S3 Bucket": AWS S3 Bucket URI  
     Ex: s3://<<S3 Bucket Name>>/AWSLogs/
    "GuardDutyFolderName" : Folder Name for the GuardDuty Findings
    "CustomLogTableName": Azure Log Analytics Custom Log Table Name		
    

Post Deployment Steps

  1. The TimerTrigger makes it incredibly easy to have your functions executed on a schedule. This sample demonstrates a simple use case of calling your function based on your schedule provided while deploying. If the time interval needs to be modified, it is recommended to change the Function App Timer Trigger accordingly update environment variable "Schedule" (post deployment) to prevent overlapping data ingestion.

    a.	Go to your Resource Group --> Click on Function App `<<functionappname>><<uniqueid>>`
    b.	Click on Function App "Configuration" under Settings 
    c.	Click on "Schedule" under "Application Settings"
    d.	Update your own schedule using cron expression.
    

    Note: For a TimerTrigger to work, you provide a schedule in the form of a cron expression(See the link for full details). A cron expression is a string with 6 separate expressions which represent a given schedule via patterns. The pattern we use to represent every 10 minutes is 0 */10 * * * *. This, in plain text, means: "When seconds is equal to 0, minutes is divisible by 10, for any hour, day of the month, month, day of the week, or year".

  2. Parameterized AWS S3 fresh event duration using environment variable "FreshEventTimeStamp". Value must be in minutes.
    Note
    Azure Function trigger schedule and FreshEventTimeStamp
    Ex: If you want to trigger function every 30 min then values must be
    FreshEventTimeStamp=10
    Schedule=0 */10 * * * *

  3. AWSAccessKey, AWSSecretAccessKey and Workspace Key will be placed as "Secrets" in the Azure KeyVault <<functionappname>><<uniqueid>> with only Azure Function access policy. If you want to see/update these secrets,

    	a. Go to Azure KeyVault "<<functionappname>><<uniqueid>>"
    	b. Click on "Access Policies" under Settings
    	c. Click on "Add Access Policy"
    		i. Configure from template : Secret Management
    		ii. Key Permissions : GET, LIST, SET
    		iii. Select Prinicpal : <<Your Account>>
    		iv. Add
    	d. Click "Save"
    
    

About

Azure Sentinel Data connector to collect AWS GuardDuty Findings from AWS S3

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages