Understanding the Datalake
The Armor data lake is a centralized repository for storing Armor collected data. With regards to vulnerabilities, 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:
| Expand |
|---|
| title | Option 1: Compliance in AMP |
|---|
|
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.
|
| Expand |
|---|
| title | Option 2: Log Search in AMP |
|---|
|
- Select a Report from the Report List and click the report name to access the details.
 Image Removed - Copy its unique report Id by navigating into the report’s detail page.
 Image Removed - Navigate to Security -> Log Search and SSO into Chaos Search.
 Image Removed - 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.
 Image Removed
- Now set the date range to encompass the report date or dates to show and click Refresh.
 Image Removed
|
Data Presentation
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:
...
...
Fields
...
Values
...
@timestamp
...
Nov 2, 2020 @ 17:27:23.779
...
@version
...
1
...
_id
...
5.83E+08
...
_index
...
1_4803_customer
...
_score
...
1
...
_type
...
doc
...
armor_metrics.input_port
...
5443
...
armor_metrics.latency.processing
...
0.112
...
armor_metrics.processing_chain
...
["KVN_V4_collector_i-095a2e7cd62db995c|2020-11-02T23:27:23Z","KVN_V4_processor_i-09425dd816b437aeb|2020-11-02T23:27:23Z"]
...
cloud.account.id
...
7.41E+11
...
cloud.instance.id
...
memcache-test-ind
...
cloud.machine.type
...
MEMCACHED
...
cloud.provider
...
aws
...
cloud.region
...
us-west-2
...
data_type
...
cspm-detections
...
document_size
...
1,819
...
event.ReportId
...
bafee260-1d44-11eb-a15a-eff990dadedf
...
event.ReportTitle
...
PCI DSS FOR R&D
...
event.ReportType
...
MANDATE
...
event.outcome
...
FAIL
...
event.reason
...
[Cluster ID, memcache-test-ind],[Subnet Group, default],[Vpc Id, vpc-95234ef0]
...
event.reference
...
https://portal.secure-stage.services/compliance/reports/controls/remediations/147
...
event.severity
...
2
...
event_uuid
...
b6611368-6641-4fcb-8b34-a999b3b07328
...
external_id
...
00000000-0000-0000-0000-000000004803
...
index_type
...
cspm-detections
...
labels.parent_id
...
1
...
logsource.origin
...
unknown
...
message_size
...
0
...
riginal_timestamp
...
Nov 2, 2020 @ 14:06:58.000
...
received_timestamp
...
Nov 2, 2020 @ 17:27:23.779
...
rule.Ctrl_Obj
...
Ensure that AWS ElastiCache Memcached clusters are not associated with default VPC
...
rule.Policy
...
Payment Card Industry Data Security Standard (PCI-DSS)
...
rule.Reqt_Lvl1
...
Regularly test security systems and processes
...
rule.Reqt_Lvl2
...
Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network.
...
rule.Reqt_Lvl3
...
Boundary Protection
...
rule.Reqt_Lvl4
...
Flaw Remediation
...
rule.Section_Lvl1
...
Requirement 11
...
rule.Section_Lvl2
...
11.4
...
rule.Section_Lvl3
...
SC-7
...
rule.Section_Lvl4
...
SI-2
...
rule.id
...
147
...
tags
...
["core_metadata_miss","customer","mismatched_tenant_external_id","cached_parent_metadata"]
...
tenant_id
...
4803
...
type
...
cspm
...
...
| theme | Midnight |
|---|
| firstline | 1 |
|---|
| linenumbers | true |
|---|
...
Understanding the Datalake
...
The Armor data lake is a centralized repository for storing Armor collected data. With regards to vulnerabilities, 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:
| Expand |
|---|
| title | Option 1: Compliance in AMP |
|---|
|
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.
|
| Expand |
|---|
| title | Option 2: Log Search in AMP |
|---|
|
- Select a Report from the Report List and click the report name to access the details.
Image Added - Copy its unique report Id by navigating into the report’s detail page.
Image Added - Navigate to Security -> Log Search and SSO into Chaos Search.
Image Added - 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.
Image Added
- Now set the date range to encompass the report date or dates to show and click Refresh.
Image Added
|
Data Presentation
...
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:
| Expand |
|---|
|
| Field | Values |
|---|
@timestamp | Nov 25, 2020 @ 07:32:27.480 | | #@version | 1 | | _id | 47741608 | | _index | 1_1024_customer | | #_score | 1 | | _type | doc | | armor_metrics.input_port | 5445 | | armor_metrics.latency.processing | 0.857 | | armor_metrics.processing_chain | ["KVN_V4_collector_i-0908b8b2b53868dc0|2020-11-25T13:32:27Z","KVN_V4_processor_i-0aa172c88f440b715|2020-11-25T13:32:28Z"] | | document_size | 3,926 | | event_uuid | 6d820110-73e5-45c9-945e-10c281fd4cb4 | | external_id | 4f5b9ab7-8e57-4993-b0fb-440cd44d11e5 | | host.hostname | ip-10-0-0-8.us-west-2.compute.internal | | host.ip | 10.0.0.8 | | host.os.full | Amazon Linux 2 | | host.os.name | Linux | | host_asset_id | 75424166 | | index_type | ecs-1.5.0-vulnerability | | labels.parent_id | 1 | | logsource.origin | unknown | | message_size | 0 | | original_timestamp | Nov 25, 2020 @ 07:32:27.233 | | received_timestamp | Nov 25, 2020 @ 07:32:27.480 | | tags | ["customer","flow_source_data_miss","default_parent_id","cached_parent_metadata"] | | tenant_id | 1024 | | vulnerability.category | ["AMAZON LINUX","PCI"] | | vulnerability.consequence | Allows unauthorized disclosure of information; allows unauthorized modification; allows disruption of service. | | vulnerability.cve | http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5188 | | vulnerability.description | Amazon Linux Security Advisory for e2fsprogs: ALAS2-2020-1509 | | vulnerability.diagnosis | <DIV> Issue Overview: <P>An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability. (<A HREF="https://access.redhat.com/security/cve/CVE-2019-5094" TARGET="_blank">CVE-2019-5094 </A>)</P><P>A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability. (<A HREF="https://access.redhat.com/security/cve/CVE-2019-5188" TARGET="_blank">CVE-2019-5188 </A>)</P> </DIV> | | vulnerability.discovery | 0 | | vulnerability.enumeration | 135 | | vulnerability.id | 352127 | | vulnerability.last_modification | Oct 29, 2020 @ 07:29:25.000 | | vulnerability.patchable | 1 | | vulnerability.pci_flag | 1 | | vulnerability.published | Oct 29, 2020 @ 07:29:25.000 | | vulnerability.reference | https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html | | vulnerability.report_id | 20201125.133227 | | vulnerability.results | Package Installed Version Required Version e2fsprogs 1.42.9-12.amzn2.0.2.x86_64 1.42.9-19.amzn2 e2fsprogs-libs 1.42.9-12.amzn2.0.2.x86_64 1.42.9-19.amzn2 libcom_err 1.42.9-12.amzn2.0.2.x86_64 1.42.9-19.amzn2 libss 1.42.9-12.amzn2.0.2.x86_64 1.42.9-19.amzn2 e2fsprogs 1.42.9-12.amzn2.0.2.x86_64 1.42.9-19.amzn2 | | vulnerability.scanner.vendor | Powered by Qualys | | vulnerability.score.base | 6.7 | | vulnerability.score.environmental | 0.0 | | vulnerability.score.temporal | 5.4 | | vulnerability.score.version | 3.0 | | vulnerability.severity | 3 | | vulnerability.solution | Please refer to Amazon advisory <A HREF="https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html" TARGET="_blank">ALAS-2020-1509</A> for affected packages and patching details, or update with your package manager. <P>Patch:<BR> Following are links for downloading patches to fix the vulnerabilities: <P> <A HREF="https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html" TARGET="_blank">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on x86_64)</A><P> <A HREF="https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html" TARGET="_blank">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on aarch64)</A><P> <A HREF="https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html" TARGET="_blank">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on src)</A><P> <A HREF="https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html" TARGET="_blank">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on i686)</A> | | vulnerability.status | Active | | vulnerability.vulnerability_type | VULNERABILITY |
|
| Expand |
|---|
|
| Code Block |
|---|
| theme | Midnight |
|---|
| firstline | 1 |
|---|
| linenumbers | true |
|---|
| {
"_score": 1,
"_type": "doc",
"_source": {
"vulnerability.enumeration": "135",
"document_size": 3926,
"@timestamp": "2020-11-25T13:32:27.480Z",
"vulnerability.published": "2020-10-29T12:29:25.000Z",
"vulnerability.results": "Package\tInstalled Version\tRequired Version\ne2fsprogs\t1.42.9-12.amzn2.0.2.x86_64\t1.42.9-19.amzn2\ne2fsprogs-libs\t1.42.9-12.amzn2.0.2.x86_64\t1.42.9-19.amzn2\nlibcom_err\t1.42.9-12.amzn2.0.2.x86_64\t1.42.9-19.amzn2\nlibss\t1.42.9-12.amzn2.0.2.x86_64\t1.42.9-19.amzn2\ne2fsprogs\t1.42.9-12.amzn2.0.2.x86_64\t1.42.9-19.amzn2",
"tenant_id": "1024",
"vulnerability.cve": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5188",
"host.os.name": "Linux",
"message_size": 0,
"vulnerability.description": "Amazon Linux Security Advisory for e2fsprogs: ALAS2-2020-1509",
"vulnerability.scanner.vendor": "Powered by Qualys",
"_id": 47741608,
"tags": "[\"customer\",\"flow_source_data_miss\",\"default_parent_id\",\"cached_parent_metadata\"]",
"armor_metrics.processing_chain": "[\"KVN_V4_collector_i-0908b8b2b53868dc0|2020-11-25T13:32:27Z\",\"KVN_V4_processor_i-0aa172c88f440b715|2020-11-25T13:32:28Z\"]",
"vulnerability.score.temporal": "5.4",
"vulnerability.solution": "Please refer to Amazon advisory <A HREF=\"https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html\" TARGET=\"_blank\">ALAS-2020-1509</A> for affected packages and patching details, or update with your package manager.\n<P>Patch:<BR>\nFollowing are links for downloading patches to fix the vulnerabilities:\n<P> <A HREF=\"https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html\" TARGET=\"_blank\">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on x86_64)</A><P> <A HREF=\"https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html\" TARGET=\"_blank\">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on aarch64)</A><P> <A HREF=\"https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html\" TARGET=\"_blank\">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on src)</A><P> <A HREF=\"https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html\" TARGET=\"_blank\">ALAS-2020-1509: Amazon Linux 2 (e2fsprogs (1.42.9-19.amzn2) on i686)</A>",
"armor_metrics.input_port": "5445",
"original_timestamp": "2020-11-25T13:32:27.233Z",
"logsource.origin": "unknown",
"vulnerability.score.environmental": "0.0",
"vulnerability.status": "Active",
"vulnerability.category": "[\"AMAZON LINUX\",\"PCI\"]",
"host.ip": "10.0.0.8",
"vulnerability.discovery": "0",
"vulnerability.reference": "https://alas.aws.amazon.com/AL2/ALAS-2020-1509.html",
"vulnerability.report_id": "20201125.133227",
"received_timestamp": "2020-11-25T13:32:27.480Z",
"host.os.full": "Amazon Linux 2",
"vulnerability.pci_flag": "1",
"vulnerability.patchable": "1",
"vulnerability.score.version": "3.0",
"event_uuid": "6d820110-73e5-45c9-945e-10c281fd4cb4",
"vulnerability.last_modification": "2020-10-29T12:29:25.000Z",
"vulnerability.diagnosis": "<DIV>\n Issue Overview:\n <P>An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability. (<A HREF=\"https://access.redhat.com/security/cve/CVE-2019-5094\" TARGET=\"_blank\">CVE-2019-5094 </A>)</P><P>A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability. (<A HREF=\"https://access.redhat.com/security/cve/CVE-2019-5188\" TARGET=\"_blank\">CVE-2019-5188 </A>)</P>\n </DIV>\n\n ",
"labels.parent_id": "1",
"host_asset_id": "75424166",
"vulnerability.vulnerability_type": "VULNERABILITY",
"external_id": "4f5b9ab7-8e57-4993-b0fb-440cd44d11e5",
"vulnerability.score.base": "6.7",
"armor_metrics.latency.processing": 0.8566529750823975,
"vulnerability.severity": "3",
"vulnerability.consequence": "Allows unauthorized disclosure of information; allows unauthorized modification; allows disruption of service.",
"@version": 1,
"host.hostname": "ip-10-0-0-8.us-west-2.compute.internal",
"index_type": "ecs-1.5.0-vulnerability",
"vulnerability.id": "352127"
},
"_id": "3024689447741608",
"_index": "1_21771024_customer"
} |
|
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:
...
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.
...