Analytics Story: Dev Sec Ops
Description
This story is focused around detecting attacks on a DevSecOps lifeccycle which consists of the phases plan, code, build, test, release, deploy, operate and monitor.
Why it matters
DevSecOps is a collaborative framework, which thinks about application and infrastructure security from the start. This means that security tools are part of the continuous integration and continuous deployment pipeline. In this analytics story, we focused on detections around the tools used in this framework such as GitHub as a version control system, GDrive for the documentation, CircleCI as the CI/CD pipeline, Kubernetes as the container execution engine and multiple security tools such as Semgrep and Kube-Hunter.
Correlation Search
1`risk_index` | fillnull | stats sum(risk_score) as risk_score values(source) as signals values(repository) as repository by user | sort - risk_score | where risk_score > 80 | `correlation_by_user_and_risk_filter`
Detections
Data Sources
Name | Platform | Sourcetype | Source |
---|---|---|---|
ASL AWS CloudTrail | AWS | aws:asl |
aws_asl |
AWS CloudTrail DescribeImageScanFindings | AWS | aws:cloudtrail |
aws_cloudtrail |
AWS CloudTrail PutImage | AWS | aws:cloudtrail |
aws_cloudtrail |
CircleCI | N/A | circleci |
circleci |
G Suite Drive | N/A | gsuite:drive:json |
http:gsuite |
G Suite Gmail | N/A | gsuite:gmail:bigquery |
http:gsuite |
GitHub | AWS | aws:firehose:json |
github |
References
Source: GitHub | Version: 1