si-4-system-monitoring

name	SI-4_system-monitoring
description	Monitor the system to detect: Attacks and indicators of potential attacks in accordance with the following monitoring objectives: [organization-define
category	input-validation
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","si-4","si"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-20"]
chains_with	["AC-2","AC-3","AC-4","AC-8","AC-17","AU-2","AU-6","AU-7","AU-9","AU-12"]
prerequisites	[]
severity_boost	{"AC-2":"Chain with AC-2 for comprehensive security coverage","AC-3":"Chain with AC-3 for comprehensive security coverage","AC-4":"Chain with AC-4 for comprehensive security coverage"}

SI-4 System Monitoring

High-Level Description

Family: System and Information Integrity (SI) Framework: NIST SP 800-53 Rev 5

System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at external interfaces to the system. Internal monitoring includes the observation of events occurring within the system. Organizations monitor systems by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives guide and inform the determination of the events. System monitoring capabilities are achieved through a variety of tools and techniques, including intrusion detection and prevention systems, malicious code protection software, scanning tools, audit record monitoring software, and network monitoring software.

Depending on the security architecture, the distribution and configuration of monitoring devices may impact throughput at key internal and external boundaries as well as at other locations across a network due to the introduction of network throughput latency. If throughput management is needed, such devices are strategically located and deployed as part of an established organization-wide security architecture. Strategic locations for monitoring devices include selected perimeter locations and near key servers and server farms that support critical applications. Monitoring devices are typically employed at the managed interfaces associated with controls SC-7 and AC-17 . The information collected is a function of the organizational monitoring objectives and the capability of systems to support such objectives. Specific types of transactions of interest include Hypertext Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. System monitoring is an integral part of organizational continuous monitoring and incident response programs, and output from system monitoring serves as input to those programs. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other controls (e.g., AC-2g, AC-2(7), AC-2(12)(a), AC-17(1), AU-13, AU-13(1), AU-13(2), CM-3f, CM-6d, MA-3a, MA-4a, SC-5(3)(b), SC-7a, SC-7(24)(b), SC-18b, SC-43b ). Adjustments to levels of system monitoring are based on law enforcement information, intelligence information, or other sources of information. The legality of system monitoring activities is based on applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.