Information System Continuous Monitoring (ISCM)

1. FITSP-M Module 7 Information System Continuous Monitoring (ISCM)

2. Leadership “Continuous monitoring is the backbone of true security.” -VivekKundra Federal CIO

3. FITSP-M Exam Module Objectives • Audit and Accountability • Manage controls in a system that facilitate the creation, protection, and retention of information system audit records to the extent needed to enable the monitoring, analysis, and investigation of the system • Security Assessments and Authorization • Supervise processes that facilitate the monitoring of information system security controls on an ongoing basis to ensure the continued effectiveness of the controls • System and Communication Protection • Oversee processes that monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems • System and Information Integrity • Direct mechanisms that monitor information system security alerts and advisories that take appropriate actions in response

4. Continuous Monitoring Overview • Section A: Continuous Monitoring Trends • RMF Step 6 – Monitor Security Controls • Redefining Risk Management • DHS CM Reporting Metrics • Cyberscope • Section B: CM Guidelines, SP 800-137 • ISCM Fundamentals • Organization-wide Approach • Elements of Organization-wide CM Program • Continuous Monitoring Process • Section C: Automation • Automation Domains • SCAP & OCIL • Continuous Asset Evaluation, Situational Awareness and Risk Scoring (CEASARS) • Section D: CM Implementation

5. Section A Continuous Monitoring Trends

6. RMF Step 6 – Monitor Security Controls • Information System And Environment Changes • Ongoing Security Control Assessments • Ongoing Remediation Actions • Key Updates • Security Status Reporting • Ongoing Risk Determination And Acceptance • Information System Removal And Decommissioning

7. Redefined Risk Management OODA Loop

8. DHS Cyberscope • Monthly Data Feeds to DHS • Inventory • Systems and Services • Hardware • Software • External Connections • Security Training • Identity Management and Access • Government-wide benchmarking on security posture • Agency-specific interviews

9. DHS FY12 Reporting Metrics1. Continuous Monitoring

10. Knowledge Check • Name the components of the new risk management model. • Name the reporting tool, which automates Agency FISMA reporting directly to the DHS. • What 3 Continuous Monitoring metrics will DHS expect agencies to report for FY2012?

11. Section B The CM GuidelinesSP 800-137

12. NIST SP800-137 Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations Information security continuous monitoring (ISCM) is defined as: • Maintaining Ongoing Awareness of Information Security, Vulnerabilities, and Threats • Support Organizational Risk Management Decisions • Begins With Leadership Defining A Comprehensive ISCM Strategy Encompassing • technology • processes • procedures • operating environments • people

13. ISCM Fundamentals • Define the ISCM strategy • Establish an ISCM program • Implement the ISCM program • Analyze and Report findings • Respond to findings • Review and Update ISCM strategy and program

14. ISCM Criteria Risk Management Strategy: How the organization plans to assess, respond to, and monitor risk Oversight required to ensure effectiveness of RM strategy Tier 1 Organization Automated/Manual Data Feeds (Security-related Information, POAMs, SARs) Program Management Defined by how business processes are prioritized Types of information needed to successfully execute those business processes Tools Data Tier 2 Mission/Business Processes Tools • Monitoring System Level Controls and Security Status Reporting • Security Alerts • Security Incidents • Identified Threat Activities Tier 3 Data Information Systems

15. The CM Process • Define an ISCM Strategy • Establish an ISCM Program • Implement an ISCM Program • Determining Appropriate Response • Mitigating Risk • Review and Update the Monitoring Program

16. Interrelationships to the CM Process • Risk Tolerance • Enterprise Architecture • Security Architecture • Security Configurations • Plans for Changes to Enterprise Architecture • Available Threat Information

17. Section C Automation

18. Role of Automation in ISCM • Consideration is given to ISCM tools that: • Pull information from a variety of sources (Specifications, Mechanisms, Activities, Individuals) • Use open specifications such as SCAP • Offer interoperability with other products (help desk, inventory management, configuration management, and incident response solutions) • Support compliance with applicable federal laws, regulations, standards, and guidelines • Provide reporting with the ability to tailor output • Allow for data consolidation into Security Information and Event Management (SIEM) tools and dashboard products. SP 800-137

19. Security Automation Domains • Vulnerability & Patch Management • Event & Incident Management • Malware Detection • Asset Management • Configuration Management • Network Management • License Management • Information Management • Software Assurance SP 800-137

20. SP 800-137

21. SP 800-137

22. Software Assurance TechnologiesSecurity Automation Domain #11 • Software Assurance Automation Protocol (SwAAP -measure and enumerate software weaknesses): SP 800-137

23. Knowledge Check • What is the document that provides guidelines for developing a CM program? • What is the first step in the CM Process? • Name an automation specification, which is a dictionary of weaknesses that can lead to exploitable vulnerabilities? • What is defined as an information security area that includes a grouping of tools, technologies, and data?Data within the domains is captured, correlated, analyzed, and reported to present the security status of the organization that is represented by the domains monitored.

24. Automation and Reference Data Sources • Security Content Automation Protocol (SCAP) • What Can Be Automated With SCAP • How to Implement SCAP • Partially Automated Controls • Reference Data Sources • National Vulnerability Database (NVD) • Security Configuration Checklists

25. NVD Primary Resources Vulnerability Search Engine National Checklist Program SCAP Compatible Tools SCAP Data Feeds (CVE, CCE, CPE, CVSS, XCCDF, OVAL) Product Dictionary (CPE) Impact Metrics (CVSS) Common Weakness Enumeration (CWE) SCAP Program Scan NVD Data Feed

26. SCAP: What Can Be Automated? • Vulnerability and Patch Scanners • Authenticated • Unauthenticated • Baseline Configuration Scanners • Federal Desktop Core Configuration (FDCC) • United States Government Configuration Baseline (USGCB)

27. How to Implement SCAP with SCAP-validated Tools

28. … and SCAP-expressed Checklists

29. Partially Automated Controls • Open Checklist Interactive Language (OCIL) • Define Questions (Boolean, Choice, Numeric, Or String) • Define Possible Answers to a Question from Which User Can Choose • Define Actions to be Taken Resulting from a User's Answer • Enumerate Result Set • Used in Conjunction with eXtensible Configuration Checklist Description Format (XCCDF)

30. Technologies for Aggregation and Analysis • Management Dashboards • Meaningful And Easily Understandable Format • Provide Information Appropriate to Roles And Responsibilities • Security Information and Event Management (SIEM), analysis of: • Vulnerability Scanning Information, • Performance Data, • Network Monitoring, • System Audit Record (Log) Information • Audit Record Correlation And Analysis

31. CAESARS Framework

33. IR 7756

34. CM Documents

35. Knowledge Check • Name the set of specifications used to standardize the communication of software flaws and security configurations. • What is the name of the U.S. government repository of standards-based vulnerability management data represented using the SCAP specifications? • What is the name of the program designed to test the ability of products to use the features and functionality available through SCAP and its component standards? • Name an ISCM reference model that provides a foundation for a continuous monitoring reference model that aims to enable organizations to aggregate collected data from across a diverse set of security tools, analyze that data, perform scoring, enable user queries, and provide overall situational awareness.

36. Section D CM Implementation

39. Monitoring Tool Data Sources

40. Risk Scoring

41. Remediation

42. CM Challenges • The Organization of the SP 800-53 • Emerging CM Technologies • SCAP • OCIL • The Limitations of CAESARS • Department of State’s iPost and Risk Scoring Program

43. Section Optional CM Discussion

44. Organization of Security Controls 18 Families 198 Controls 892 Control Items (Parts/Enhancements)

45. Control Catalog Redundancies Evident in USGCB

46. DoD Solution: Mapping STIG to 800-53

47. DoS Solution: Using Fishbone to Find Root Controls

48. DoS Solution: Proposed Structure of Security Control Catalog

49. The Limitations of CAESARS • Lack of Interface Specifications • Reliance on an Enterprise Service Bus • Incomplete Communication Payload Specifications • Lack of Specifications Describing Subsystem Capabilities • Lack of a Multi-CM Instance Capability • Lack of Multi-Subsystem Instance Capability • CM Database Integration with Security Baseline Content • Lack of Detail on the Required Asset Inventory • Requirement for Risk Measurement

50. GAO Report on Scope of iPost Risk Scoring Program • Addresses windows hosts but not other IT assets on its major unclassified network • Covers a set of 10 scoring components that includes some, but not all, information system controls that are intended to reduce risk • State could not demonstrate the extent to which scores are based on risk factors such as threat, impact, or likelihood of occurrence that are specific to its computing environment