Benchmark: Information System Monitoring (SI-4)
Description
The organization: a.Monitors the information system to detect: 1. Attacks and indicators of potential attacks in accordance with [Assignment: organization-defined monitoring objectives]; and 2.Unauthorized local, network, and remote connections; b. Identifies unauthorized use of the information system through [Assignment: organization-defined techniques and methods]; c. Deploys monitoring devices: 1. Strategically within the information system to collect organization-determined essential information; and 2. At ad hoc locations within the system to track specific types of transactions of interest to the organization; d. Protects information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion; e. Heightens the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations and assets, individuals, other organizations, or the Nation based on law enforcement information, intelligence information, or other credible sources of information; f. Obtains legal opinion with regard to information system monitoring activities in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations; and g. Provides [Assignment: organization-defined information system monitoring information] to [Assignment: organization-defined personnel or roles] [Selection (one or more): as needed; [Assignment: organization-defined frequency]].
Usage
Browse dashboards and select Information System Monitoring (SI-4):
steampipe dashboard
Or run the benchmarks in your terminal:
steampipe check aws_compliance.benchmark.nist_800_53_rev_4_si_4
Snapshot and share results via Steampipe Cloud:
steampipe loginsteampipe check --share aws_compliance.benchmark.nist_800_53_rev_4_si_4
Benchmarks
- SI-4(1) System-Wide Intrusion Detection System
- SI-4(2) Automated Tools For Real-Time Analysis
- SI-4(4) Inbound and Outbound Communications Traffic
- SI-4(5) System-Generated Alerts
- SI-4(16) Correlate Monitoring Information
Controls
- CloudTrail trails should be integrated with CloudWatch logs
- CloudWatch alarm should have an action configured
- EC2 instance detailed monitoring should be enabled
- ELB application load balancers should have Web Application Firewall (WAF) enabled
- GuardDuty should be enabled
- GuardDuty findings should be archived
- AWS Security Hub should be enabled for an AWS Account
- Logging should be enabled on AWS WAFv2 regional and global web access control list (ACLs)