1 / 54

US Federal ICS Security Standards and Guidelines Overview

US Federal Industrial Control System (ICS) Security Standards and Guidelines Keith Stouffer National Institute of Standards and Technology (NIST) June 26, 2007. US Federal ICS Security Standards and Guidelines Overview. FISMA NIST SP 800-53 NIST SP 800-53A NIST SP 800-82.

beau-serrano
Download Presentation

US Federal ICS Security Standards and Guidelines Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. US Federal Industrial Control System (ICS) Security Standards and GuidelinesKeith StoufferNational Institute of Standards and Technology (NIST)June 26, 2007

  2. US Federal ICS Security Standards and Guidelines Overview • FISMA • NIST SP 800-53 • NIST SP 800-53A • NIST SP 800-82

  3. FISMA LegislationOverview “Each federal agency shall develop, document, and implement an agency-wide information security program to provide information security for the information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor, or other source…” -- Federal Information Security Management Act of 2002

  4. US Federal Standards and Guidelines • Federal Information Processing Standards (FIPS) • Special Publication (SP) 800 Series documents

  5. Federal Information Standards (FIPS) • Approved by the Secretary of Commerce • Compulsory and binding standards for federal agencies non-national security information systems • Voluntary adoption by federal national security community and private sector

  6. Special Publication (SP) 800 Series Documents • Special Publications in the 800 series are documents of general interest to the computer security community • Established in 1990 to provide a separate identity for information technology security publications. • Reports on guidance, research, and outreach efforts in computer security, and collaborative activities with industry, government, and academic organizations • Agencies must follow NIST 800 series guidance documents; but 800 series documents generally allow agencies some latitude in their application

  7. Scope of Applicability • All federal information systems other than those systems designated as national security systems as defined in 44 U.S.C., Section 3542.* • State, local, and tribal governments, as well as private sector organizations that compose the critical infrastructure of the United States on a voluntary basis, as appropriate. * The guidelines have been broadly developed from a technical perspective to complement similar guidelines for national security systems.

  8. RMF Characteristics • The NIST Risk Management Framework and the associated security standards and guidance documents provide a process that is: • Disciplined • Flexible • Extensible • Repeatable • Organized • Structured “Building information security into the infrastructure of the organization… so that critical enterprise missions and business cases will be protected.”

  9. Managing Enterprise Risk • Key activities in managing enterprise-level risk—risk to the enterprise and to other organizations resulting from the operation of an information system: • Categorize the information system (criticality/sensitivity) • Select and tailor baseline (minimum) security controls • Supplement the security controls based on risk assessment • Document security controls in system security plan • Implement the security controls in the information system • Assess the security controls for effectiveness • Authorize information system operation based on mission risk • Monitor security controls on a continuous basis

  10. Starting Point FIPS 199 / SP 800-60 SP 800-37 / SP 8800-53A FIPS 200 / SP 800-53 Security Categorization Security Control Monitoring Security Control Selection Define criticality /sensitivity of information system according to potential impact of loss Continuously track changes to the information system that may affect security controls and reassess control effectiveness Select minimum (baseline) security controls to protect the information system; apply tailoring guidance as appropriate SP 800-37 FIPS 200 / SP 800-53 / SP 800-30 System Authorization Security Control Refinement Determine risk to agency operations, agency assets, or individuals and, if acceptable, authorize information system operation Use risk assessment results to supplement the tailored security control baseline as needed to ensure adequate security and due diligence SP 800-53A SP 800-18 SP 800-70 Security Control Assessment Security Control Documentation Security Control Implementation Determine security control effectiveness (i.e., controls implemented correctly, operating as intended, meeting security requirements) Document in the security plan, the security requirements for the information system and the security controls planned or in place Implement security controls; apply security configuration settings The Risk Management Framework

  11. SP 800-60 Security Categorization Example: A Pulp and Paper Control System Guidance for Mapping Types of Information and Information Systems to FIPS Publication 199 Security Categories

  12. FIPS 200 SP 800-53 Security Categorization Example: A Pulp and Paper Control System Minimum Security Controls for Moderate Impact Systems

  13. SP 800-53 ICS Master Security Control Catalog Complete Set of Security Controls and Control Enhancements Minimum Security Controls Low Impact Information Systems Minimum Security Controls Moderate Impact Information Systems Minimum Security Controls High Impact Information Systems Baseline #1 Baseline #2 Baseline #3 Selection of a subset of security controls from the master catalog—consisting of basic level controls Builds on low baseline. Selection of a subset of controls from the master catalog—basic level controls, additional controls, and control enhancements Builds on moderate baseline. Selection of a subset of controls from the master catalog—basic level controls, additional controls, and control enhancements Security Control Baselines

  14. Minimum Security Controls • Minimum security controls, or baseline controls, defined for low-impact, moderate-impact, and high-impact information systems— • Provide a starting point for organizations in their security control selection process • Are used in conjunction with tailoring guidance that allows the baseline controls to be adjusted for specific operational environments • Support the organization’s risk management process

  15. Minimum Security Controls Low Impact Information Systems Minimum Security Controls Moderate Impact Information Systems Minimum Security Controls High Impact Information Systems Enterprise #1 Operational Environment #1 Enterprise #2 Operational Environment #2 Enterprise #3 Operational Environment #3 Low Baseline Moderate Baseline High Baseline Tailored Security Controls Tailored Security Controls Tailored Security Controls Cost effective, risk-based approach to achieving information security… Tailoring Security ControlsScoping, Parameterization, and Compensating Controls

  16. Categorization Issues • Currently, categorization of Federal systems is mostly based on the information that is used within the information system, rather the information system itself • Categorization workshop at NIST, September 5-6, 2007 to discuss categorization methodologies for ICS

  17. Low Impact System

  18. Moderate Impact Systems

  19. High Impact System

  20. High Impact System !!!

  21. More High Impact Systems 

  22. NIST SP 800-53 • NIST SP 800-53 Recommended Security Controls for Federal Information Systems, which was developed for traditional IT systems, contains mandatory information security requirements for all non-national security information and information systems that are owned, operated, or controlled by federal agencies. • NIST SP 800-53 provides the security controls that need to be applied to secure the system. It does now specify how the controls need to be implemented.

  23. NIST SP 800-53 ICS Structure 17 Control Families171 Controls (Requirements) • Access Control • Awareness and Training • Audit and Accountability • Certification, Accreditation, and Security Assessments • Configuration Management • Contingency Planning • Identification and Authentication • Incident Response • Maintenance • Media Protection • Physical and Environmental • Planning • Personnel Security • Risk Assessment • Systems and Services Acquisition • System and Communications Protection • System and Information

  24. Technical Control Families Possible Reference for Part 4 • Access Control (20 requirements) • Audit and Accountability (11 requirements) • Identification and Authentication (7 requirements) • System and Communications Protection (23 requirements) • TOTAL (61 requirements)

  25. Operational Control Families Possible Reference for Part 2 and/or Part 3 • Awareness and Training (5 requirements) • Configuration Management (8 requirements) • Contingency Planning (10 requirements) • Incident Response (7 requirements) • Maintenance (6 requirements) • Media Protection (6 requirements) • Physical and Environmental Protection (19 requirements) • Personnel Security (8 requirements) • System and Information Integrity (12 requirements) • TOTAL (81 requirements)

  26. Management Control Families Possible Reference for Part 2 and/or Part 3 • Certification, Accreditation, (7 requirements) and Security Assessments • Planning (6 requirements) • Risk Assessment (5 requirements) • System and Services Acquisition(11 requirements) • TOTAL (29 requirements)

  27. Control Structure • The security control structure consists of three key components: (i) a control section (ii) a supplemental guidance section – there may also be an ICS supplemental guidance section (iii) a control enhancements section

  28. Control Example AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. Supplemental Guidance: Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. Control Enhancements: (1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities. (2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].

  29. Control Example AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. Supplemental Guidance: Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. Control Enhancements: (1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities. (2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].

  30. Control • The control section provides a concise statement of the specific security capability needed to protect a particular aspect of an information system. The control statement describes specific security-related activities or actions to be carried out by the organization or by the information system. For some controls in the control catalog, a degree of flexibility is provided by allowing organizations to selectively define input values for certain parameters associated with the controls.

  31. Control Example AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. Supplemental Guidance: Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. Control Enhancements: (1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities. (2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].

  32. Supplemental Guidance • The supplemental guidance section provides additional information related to a specific security control. Organizations should consider supplemental guidance when defining, developing, and implementing security controls.

  33. ICS Supplemental Guidance • ICS Supplemental Guidance provides additional guidance on how to apply the control, or provides guidance as to why the control may not be applicable in ICS environments.

  34. Control Example AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. Supplemental Guidance: Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. Control Enhancements: (1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities. (2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].

  35. Control Enhancement • The control enhancements section provides statements of security capability to: (i) build in additional, but related, functionality to a basic control; and/or (ii) increase the strength of a basic control. In both cases, the control enhancements are used in an information system requiring greater protection due to the potential impact of loss or when organizations seek additions to a basic control’s functionality based on the results of a risk assessment. Control enhancements are numbered sequentially within each control so the enhancements can be easily identified when selected to supplement the basic control.

  36. Control Example AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. Supplemental Guidance: Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. Control Enhancements: (1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities. (2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].

  37. Baselines • LOW Baseline - Selection of a subset of security controls from the master catalog consisting of basic level controls • MOD Baseline - Builds on LOW baseline. Selection of a subset of controls from the master catalog—basic level controls, additional controls, and control enhancements • HIGH Baseline - Builds on MOD baseline. Selection of a subset of controls from the master catalog—basic level controls, additional controls, and control enhancements Question: How are the three SP 800-53 baselines and the three ISA 99 security levels related? Can these be used as a reference for 99.04?

  38. Key Question #1 • What security controls are needed to adequately protect an information system that supports the operations and assets of the organization? • FIPS Pub 199, FIPS Pub 200, NIST Special Publication 800-60, and NIST Special Publication 800-53 guide actions. • Decisions result in an agreed upon set of security controls and acceptance of any residual risk documented in the information system security plan and approved by organizational officials.

  39. Control Example AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. Supplemental Guidance: Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. Control Enhancements: (1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities. (2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].

  40. Key Question #2 • To what extent are the security controls implemented correctly, operating as intended, and producing the desired outcome with respect to meeting information security requirements? • NIST Special Publications 800-37 and 800-53A guide actions. • Decisions result in determination of security control effectiveness and acceptance of mission/business function risk to the organization.

  41. Compliance (800-53A) AU-6 AUDIT MONITORING, ANALYSIS, AND REPORTING Control: The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions. ASSESSMENT OBJECTIVE: Determine if: (i) the organization regularly reviews/analyzes audit records for indications of inappropriate or unusual activity; (ii) the organization investigates suspicious activity or suspected violations; (iii) the organization reports findings of inappropriate/usual activities, suspicious behavior, or suspected violations to appropriate officials; and (iv) the organization takes necessary actions in response to the reviews/analyses of audit records. ASSESSMENT METHODS AND OBJECTS: Examine (DEPTH, COVERAGE): Audit and accountability policy; procedures addressing audit monitoring, analysis, and reporting; reports of audit findings; records of actions taken in response to reviews/analyses of audit records; other relevant documents or records. Test (DEPTH, COVERAGE): Information system audit monitoring, analysis, and reporting capability.

  42. Federal Agency Challenges • Federal agencies required to apply NIST SP 800-53 Recommended Security Controls for Federal Information Systems (general IT security requirements) to their ICSs • Federal agencies that own/operate electric power-related ICSs could potentially have to meet 2 standards (FIPS 200/NIST SP 800-53 and FERC standards*) *Most mature industry candidate is the NERC CIPs

  43. NIST Industrial Control System Security Project • Joint MEL/ITL project, in collaboration with federal and industry stakeholders, to develop standards, guidelines and test methods to help secure these critical control systems in harmony with their demanding safety and reliability requirements. http://csrc.nist.gov/sec-cert/ics

  44. ICS Security Project Strategy • Work with government and industry ICS community to foster convergence of ICS security requirements • DHS, DoE, FERC, DoI, ICS agencies (BPA, SWPA, WAPA) • Industry standards groups • ISA SP99 Industrial Automation and Control System Security standard • IEC 62443 Security for industrial process measurement and control –Network and system security standard

  45. Federal ICS Workshops • Workshop April 19-20, 2006 at NIST to discuss the development of security requirements and baseline security controls for federally owned/operated ICS based on NIST SP 800-53 • Workshop March 27-28, 2007 at NIST to discuss and vet draft security requirements and baseline security controls for federally owned/operated ICS based on NIST SP 800-53 • Initial public draft scheduled for release summer 2007

  46. Federal ICS Workshops • Attended by Federal stakeholders • Bonneville Power Administration (BPA) • Southwestern Power Administration (SWPA) • Tennessee Valley Authority (TVA) • Western Area Power Administration (WAPA) • Federal Aviation Administration (FAA) • Department of the Interior, Bureau of Reclamation • Department of Energy (DOE) • DOE Labs (Argonne, Idaho, Pacific Northwest, Sandia) • Federal Energy Regulatory Commission (FERC) • Department of Homeland Security (DHS)

  47. NIST SP 800-53 ICS • Draft NIST SP 800-53 ICS: • http://csrc.nist.gov/sec-cert/ics/papers/AppxF_800-53-rev1-Augmented_12Jun07.pdf • Draft NIST SP 800-53 ICS Baselines: • http://csrc.nist.gov/sec-cert/ics/papers/ICS-Requirements-Baselines.pdf • First Public Draft of these documents scheduled for release summer 2007

  48. NIST Workshop on Applying NIST SP 800-53 to ICS • NIST Workshop on Applying NIST SP 800-53 ICS, August 16 – 17, following the Control System Cyber Security Conference, Knoxville, TN • NIST will host a workshop for representatives from national and international industrial control system (ICS) communities (e.g. electric, oil, gas, water, manufacturing) to share information, obtain direct inputs, and determine their level of interest in voluntarily adopting and using NIST’s ICS augmentation of NIST SP 800-53

  49. SP800-53/NERC CIP Mappings • Developed a bi-directional mapping and gap analysis between NIST SP800-53 and the NERC CIP standard to discover and propose modifications to remove any conflicts • Generally, conforming to moderate baseline in SP 800-53 complies with the management, operational and technical security requirements of the NERC CIPs; the converse is not true. • Full report available at: http://csrc.nist.gov/sec-cert/ics/papers/ICS-in-SP800-53_final_21Mar07.pdf

  50. SP800-53/NERC CIP Mapping Table (Small Section of Actual Table)

More Related