Understanding the Datalake
The Armor data lake is a centralized repository for storing Armor collected data. With regards to CSPM, the data lake contains all the data for every report created for an environment and all the historical data from when the reports are run. This can be a lot of data so narrowing down the scope of information is critical to making sense of it all.
Accessing the Datalake
Users can access the datalake in two ways:
Select a Report from the Report List and click on it’s name to access the details page.
Then expand down to the control level of a section to view links for Remediation and Advanced Query.
Click on Advanced Query.
This opens ChaosSearch in a new window.
Click on the Single Sign On button.
Click Next again on the next page to sign in to ChaosSearch.
Once the page loads the following will show:
Note that there are two filters already being applied based on which control was open when Advanced Query was selected. The ruleId and ReportId.
To see the complete report, click on the X next to the rule.Id and now the filter is only using the ReportId to get data.
Keeping the rule.Id can also be useful for comparing changes over time (using a wider date range) for that rule.
Changing the date range allows for viewing a single or multiple runs of the report depending on the goal.
- Select a Report from the Report List and click the report name to access the details.
- Copy its unique report Id by navigating into the report’s detail page.
- Navigate to Security -> Log Search and SSO into Chaos Search.
- Create a filter by doing the following:
- Click on Add filter.
- In Field select event.ReportId
- Select is for Operator.
- Paste the report Id from the report details page into the Value field.
- Click Save.
- Now set the date range to encompass the report date or dates to show and click Refresh.
Data consists of documents stored in the datalake. Each document contains all the data related to that particular rule and resource. Below are examples of the table and JSON views:
Nov 2, 2020 @ 17:27:23.779
PCI DSS FOR R&D
[Cluster ID, memcache-test-ind],[Subnet Group, default],[Vpc Id, vpc-95234ef0]
Nov 2, 2020 @ 14:06:58.000
Nov 2, 2020 @ 17:27:23.779
Ensure that AWS ElastiCache Memcached clusters are not associated with default VPC
Payment Card Industry Data Security Standard (PCI-DSS)
Regularly test security systems and processes
Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network.
The schema for these documents is based on Elastic Common Schema, please refer to the below links for the details and explanation of the fields:
cloud schema - https://www.elastic.co/guide/en/ecs/current/ecs-cloud.html
Reqt_Lvl1 - Top level requirement
Section_Lvl1 - Top level section name
Reqt_Lvl2 - Second level requirement
Section_Lvl2 - Second level section name
Reqt_Lvl3 - Third level requirement
Section_Lvl3 - Third level section name
Reqt_Lvl4 - Fourth level requirement
Section_Lvl4 - Fourth level section name
Policy - the mandate selected at the time of report creation
event schema - https://www.elastic.co/guide/en/ecs/current/ecs-rule.html
Report Id - the unique Guid of the report generated
Report Title - the title used when creating the report
Helpful Fields for Searching the Datalake
the cloud provider type (AWS, Google or Azure)
a specific cloud account Id as reports may contain more than one account
the instance id
a specific report id as multiple reports may exist
whether the resource Passed/Failed
a specific policy
Adding a Filter
To add additional filters, click on the Add Filter Button.
Then set the field to one of the helpful fields above, select the operator, put in the value and hit save. The data is now filtered on a specific reportId, rPolicy or other field selected.
Viewing Datalake Aggregations
Please refer to Reports for custom aggregations, visualizations and custom reports.
Was this helpful?