1 / 14

Information System Security Assurance Architecture A Proposed IEEE Standard for Managing Enterprise Risk

Information System Security Assurance Architecture A Proposed IEEE Standard for Managing Enterprise Risk. February 7, 2005 Dr. Ron Ross Computer Security Division Information Technology Laboratory National Institute of Standards and Technology. The Information Age.

alicia
Télécharger la présentation

Information System Security Assurance Architecture A Proposed IEEE Standard for Managing Enterprise Risk

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. Information System Security Assurance ArchitectureA Proposed IEEE Standard for Managing Enterprise Risk February 7, 2005 Dr. Ron Ross Computer Security Division Information Technology Laboratory National Institute of Standards and Technology

  2. The Information Age • Information systems are an integral part of government and business operations today • Information systems are changing the way we do business and interact as a society • Information systems are driving a reengineering of business processes in all sectors including defense, healthcare, manufacturing, financial services, etc. • Information systems are driving a transition from a paper-based society to a digital society

  3. The Protection Gap • Information system protection measures have not kept pace with rapidly advancing technologies • Information security programs have not kept pace with the aggressive deployment of information technologies within enterprises • Two-tiered approach to security (i.e., national security community vs. everyone else) has left significant parts of the critical infrastructure vulnerable

  4. The Global Threat • Information security is not just a paperwork drill…there are dangerous adversaries out there capable of launching serious attacks on our information systems that can result in severe or catastrophic damage to the nation’s critical information infrastructure and ultimately threaten our economic and national security…

  5. U.S. Critical InfrastructuresDefinition • “...systems and assets, whether physical or virtual, so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on security, national economic security, national public health and safety, or any combination of those matters.” -- USA Patriot Act (P.L. 107-56)

  6. U.S. Critical InfrastructuresExamples • Energy (electrical, nuclear, gas and oil, dams) • Transportation (air, road, rail, port, waterways) • Public Health Systems / Emergency Services • Information and Telecommunications • Defense Industry • Banking and Finance • Postal and Shipping • Agriculture / Food / Water • Chemical

  7. Critical Infrastructure Protection • The U.S. critical infrastructures are over 90% owned and operated by the private sector • Critical infrastructure protection must be a partnership between the public and private sectors • Information security solutions must be broad-based, consensus-driven, and address the ongoing needs of government and industry

  8. Scope • The proposed IEEE Information System Security Assurance Architecture (ISSAA) standard specifies the architecture of a systematic approach for managing the health/state of the security controls of an information system • The architecture includes activities for the cost-effective selection, documentation, implementation, and ongoing assessment of information system security controls and for making and maintaining system security accreditation decisions

  9. Purpose • Activities critical to societal infrastructure are highly dependent on information systems for continuity and survival • The proposed ISSAA standard will improve an organization's confidence that information system security controls are adequate and effective in protecting information and that interconnecting systems can be trusted

  10. Security Categorization Security Control Selection Security Control Monitoring System Authorization Defines security category of information system according to potential impact of loss Selects minimum security controls (i.e., safeguards and countermeasures) planned or in place to protect the information system Continuously tracks changes to the information system that may affect security controls and assesses control effectiveness Security Control Refinement Uses risk assessment to adjust minimum control set based on local conditions, required threat coverage, and specific agency requirements Determines risk to agency operations, agency assets, or individuals and, if acceptable, authorizes information system processing Security Control Documentation Security Control Implementation Security Control Assessment In system security plan, provides a an overview of the security requirements for the information system and documents the security controls planned or in place Implements security controls in new or legacy information systems; implements security configuration checklists Determines extent to which the security controls are implemented correctly, operating as intended, and producing desired outcome with respect to meeting security requirements Information System Security Assurance Architecture

  11. Plug and Play Architecture • Organizations can employ their preferred security controls, risk assessment methods, and security certification and accreditation procedures within the standardized ISSAA framework • For example, the Department of Defense may instantiate security controls from DoD Instruction 8500.2 and use the DIACAP for its preferred C&A process

  12. FIPS 199 / SP 800-60 SP 800-37 SP 800-53 / FIPS 200 SP 800-37 Security Categorization Security Control Selection System Authorization Security Control Monitoring Defines category of information system according to potential impact of loss Selects minimum security controls (i.e., safeguards and countermeasures) planned or in place to protect the information system Continuously tracks changes to the information system that may affect security controls and assesses control effectiveness SP 800-53 / FIPS 200 / SP 800-30 Security Control Refinement Uses risk assessment to adjust minimum control set based on local conditions, required threat coverage, and specific agency requirements Determines risk to agency operations, agency assets, or individuals and, if acceptable, authorizes information system processing SP 800-18 SP 800-70 SP 800-53A / SP 800-37 Security Control Documentation Security Control Implementation Security Control Assessment In system security plan, provides a an overview of the security requirements for the information system and documents the security controls planned or in place Implements security controls in new or legacy information systems; implements security configuration checklists Determines extent to which the security controls are implemented correctly, operating as intended, and producing desired outcome with respect to meeting security requirements Another ExampleUsing NIST’s Security Standards and Guidelines Starting Point

  13. Organization One Information System Organization Two Information System Business / Mission Information Flow System Security Plan System Security Plan Security Assessment Report Security Information Security Assessment Report Plan of Action and Milestones Plan of Action and Milestones Determining the risk to the first organization’s operations and assets and the acceptability of such risk Determining the risk to the second organization’s operations and assets and the acceptability of such risk The objective is to achieve visibility into prospective business/mission partners information security programs BEFORE critical/sensitive communications begin…establishing levels of security due diligence. The Desired End StateSecurity Visibility Among Business/Mission Partners

  14. Information Assurance Project P1700 – IEEE Standard for Information System Security Assurance Architecture (ISSAA) • Working Group Web Page  http://issaa.org • Project Approved: August 2004 • Working Group Chair: Jack Cole, Army Research Lab • Telephone: 410.278.9276 • Fax: 410.278.2694 • Email: jack.cole@ieee.org

More Related