TCSEC: The Orange Book. TCSEC Trusted Computer System Evaluation Criteria.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

CSE331: Introduction to Networks and Security Lecture 34 Fall 2002.
Access Control Chapter 3 Part 3 Pages 209 to 227.
Effective Design of Trusted Information Systems Luděk Novák,
Summer IAVA1 NATIONAL INFORMATION ASSURANCE TRAINING STANDARD FOR SYSTEM ADMINISTRATORS (SA) Minimum.
Secure Operating Systems Lesson 0x11h: Systems Assurance.
Security Controls – What Works
Information Security Policies and Standards
1 For System Administrators INFORMATION INFORMATION SYSTEM SECURITY INFORMATION INFORMATION SYSTEM SECURITY.
ITS Offsite Workshop 2002 PolyU IT Security Policy PolyU IT/Computer Systems Security Policy (SSP) By Ken Chung Senior Computing Officer Information Technology.
Sanjay Goel, School of Business/Center for Information Forensics and Assurance University at Albany Proprietary Information 1 Unit Outline Information.
Information Systems Security Officer
Security Engineering II. Problem Sources 1.Requirements definitions, omissions, and mistakes 2.System design flaws 3.Hardware implementation flaws, such.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
7-Access Control Fundamentals Dr. John P. Abraham Professor UTPA.
Database Auditing Models Dr. Gabriel. 2 Auditing Overview Audit examines: documentation that reflects (from business or individuals); actions, practices,
Chapter 7 Database Auditing Models
Effectively Integrating Information Technology (IT) Security into the Acquisition Process Section 5: Security Controls.
Lesson 8-Information Security Process. Overview Introducing information security process. Conducting an assessment. Developing a policy. Implementing.
1 Preparing a System Security Plan. 2 Overview Define a Security Plan Pitfalls to avoid Required Documents Contents of the SSP The profile Certification.
Security Baseline. Definition A preliminary assessment of a newly implemented system Serves as a starting point to measure changes in configurations and.
ISA 562 Internet Security Theory & Practice
Asset & Security Management Chapter 9. IT Asset Management (ITAM) Is the process of tracking information about technology assets through the entire asset.
© G. Dhillon, IS Department Virginia Commonwealth University Principles of IS Security Formal Models.
Chapter 5 – Designing Trusted Operating Systems  What makes an operating system “secure”? Or “trustworthy?  How are trusted systems designed, and which.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Service Transition & Planning Service Validation & Testing
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Security Architecture and Design Chapter 4 Part 3 Pages 357 to 377.
April 14, A Watershed Date in HIPAA Privacy Compliance: Where Should You Be in HIPAA Security Compliance and How to Get There… John Parmigiani National.
Database Security and Auditing: Protecting Data Integrity and Accessibility Chapter 7 Database Auditing Models.
Chapter 5 Network Security
Operating Systems Security Chapter Seven Prepared by: Raval, Fichadia Raval Fichadia John Wiley & Sons, Inc
Chapter 2 Securing Network Server and User Workstations.
McGraw-Hill/Irwin © 2003 The McGraw-Hill Companies, Inc., All Rights Reserved. 6-1 Chapter 6 CHAPTER 6 INTERNAL CONTROL IN A FINANCIAL STATEMENT AUDIT.
Data Governance 101. Agenda  Purpose  Presentation (Elijah J. Bell) Data Governance Data Policy Security Privacy Contracts  FERPA—The Law  Q & A.
Trusted OS Design and Evaluation CS432 - Security in Computing Copyright © 2005, 2010 by Scott Orr and the Trustees of Indiana University.
CSCE 548 Secure Software Development Security Operations.
Security fundamentals Topic 2 Establishing and maintaining baseline security.
SAM-101 Standards and Evaluation. SAM-102 On security evaluations Users of secure systems need assurance that products they use are secure Users can:
Trusted Operating Systems
Configuring, Managing and Maintaining Windows Server® 2008 Servers Course 6419A.
High Assurance Products in IT Security Rayford B. Vaughn, Mississippi State University Presented by: Nithin Premachandran.
CPT 123 Internet Skills Class Notes Internet Security Session B.
HIPAA Compliance Case Study: Establishing and Implementing a Program to Audit HIPAA Compliance Drew Hunt Network Security Analyst Valley Medical Center.
Chapter 21: Evaluating Systems Dr. Wayne Summers Department of Computer Science Columbus State University
Information Security Office: Function, Alignment in the Organization, Goals, and Objectives Presentation to Sacramento PMO March 2011 Kevin Dickey.
Access Controls Mandatory Access Control by Sean Dalton December 5 th 2008.
Chap5: Designing Trusted Operating Systems.  What makes an operating system “secure”? Or “trustworthy”?  How are trusted systems designed, and which.
Chapter 8 – Administering Security  Security Planning  Risk Analysis  Security Policies  Physical Security.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
1 Security Architecture and Designs  Security Architecture Description and benefits  Definition of Trusted Computing Base (TCB)  System level and Enterprise.
CMGT 430 OUTLET Teaching Effectively/ FOR MORE CLASSES VISIT
IT Audit for non-IT auditors Cornell Dover Assistant Auditor General 31 March 2013.
Security Architecture and Design Chapter 4 Part 4 Pages 377 to 416.
Risk Management Dr. Clive Vlieland-Boddy. Managements Responsibilities Strategy – Hopefully sustainable! Control – Hopefully maximising profits! Risk.
TCSEC: The Orange Book.
Access Control Model SAM-5.
Introduction to the Federal Defense Acquisition Regulation
Special Publication Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations Dr. Ron Ross Computer Security.
Official levels of Computer Security
The Privacy Cycle A Five-Step Process to Improve Your Privacy Culture
THE ORANGE BOOK Ravi Sandhu
County HIPAA Review All Rights Reserved 2002.
EDUCAUSE Security Professionals Conference 2018 Jason Pufahl, CISO
Guest Lecture in Acc 661 (Spring 2007) Instructor: Christopher Brown)
Drew Hunt Network Security Analyst Valley Medical Center
PLANNING A SECURE BASELINE INSTALLATION
IT OPERATIONS Session 7.
Access Control What’s New?
Presentation transcript:

TCSEC: The Orange Book

TCSEC Trusted Computer System Evaluation Criteria

TCSEC Purpose -Establish best practices -Requirements for assessing the effectiveness of security controls -Measure computing resource security -Evaluate, classify, and select systems considered for computing resources

TCSEC: Purpose Guidance – provides guidance on how to design a trusted computing system along with their associated data and services Metrics – provides a metric (classification) for determining the level of trust assigned to a computing system.

Orange Book: Metrics Measurement of a system's security is quantified using a classification system. The Classes are: D C1 & C2 B1, B2, B3 A1 A is more secure than D 2 is more secure than 1.

Orange Book: Metrics The rating system is hierarchical D applies to any system that fails to meet any of the higher level security classes. The other levels have increasing security requirements. A1 systems would be rare.

Disclaimer An A1 system is not 100% secure. The risk level is expected to be lower compared to the other levels

Metrics: C1 Identification and authentication (user id & password) DAC – (Discretionary Access Controls) – capable of enforcing access controls – Example: Basic Unix/Linux OS, user, group, other.

Metrics: C2 C1 plus Audit trails System documentation and user manuals.

Metrics B1 C2 plus Discovered weaknesses must be mitigated

Metrics B2 B1 plus Security policy must be defined and documented Access controls for all subjects and objects

Metrics: B3 B2 plus Automated imminent intrusion detection, notification and response.

Metrics: A1 B3 + System is capable of secure distribution (can be transported and delivered to a client with the assurance of being secure)

Orange Book Security Criteria Security Policy Accountability Assurance Documentation

1. Security Policy The set of rules and practices that regulate how an organization manages, protects, and distributes information.

1. Security Policy The policy is organized into subjects and objects. Subjects act upon objects Subjects – processes and users. Objects – data, directories, hardware, applications A well defined access control model determines if a subject can be permitted access to an object.

Security Policy Top secret, secret, classified, non-classified Need-to-know, job division, job rotation, NDA, etc.

2. Accountability The responsibilities of all who come in contact with the system must be well defined. Identification (… the process to identify a user) Auditing (...accumulating and reviewing log information and all actions can be traced to a subject) Organizational chart Job description contract, AUP, NDA, SLA

3. Assurance The reasonable expectation that the security policy of a trusted system has been implemented correctly and works as intended. Assurance is organized into Operational assurance Life-cycle assurance

3a. Organizational Assurance Security policy is maintained in the overall design and operation of the system. Example: Users of the system have an assurance that access controls are enforced

3b. Life-cycle Assurance Insuring the system continues to meet the security requirements over the lifetime of the system. Updates to the software and hardware must be considered The expectation that the system remains operational (is available) over its lifetime Sustainability-cycle

4. Documentation Requirements Security Features User's Guide Trusted Facility Manual Test Documentation Design Documentation

Documentation: Security Features User's Guide Aimed at the ordinary (non-privileged) users. General usage policy *Instructions on how to effectively use the system Description of relevant security features

Documentation: Trusted Facility Manual Aimed at the S.A. Staff How the system is configured and maintained Includes the day-to-day required activities Backups Reviewing security logs

Documentation: Test Documentation Instructions on how to test the required security mechanisms

Documentation: Design Documentation Define the boundaries of the system A complete description of the hardware and software. Complete system design specifications Description of access controls

The Orange Book The Orange book has been superseded by the Common Criteria