common criteria l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Common Criteria PowerPoint Presentation
Download Presentation
Common Criteria

Loading in 2 Seconds...

play fullscreen
1 / 30

Common Criteria - PowerPoint PPT Presentation


  • 139 Views
  • Uploaded on

Common Criteria. IT Security Evaluation By Sandeep Joshi. List of Terms…. List of Terms…. List of Terms. History…. Originated out of three standards ITSEC (Information Technology Security Evaluation Criteria)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Common Criteria' - frederick


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
common criteria

Common Criteria

IT Security Evaluation

By

Sandeep Joshi

Southern Methodist University

list of terms
List of Terms…

Southern Methodist University

list of terms3
List of Terms…

Southern Methodist University

list of terms4
List of Terms

Southern Methodist University

history
History…
  • Originated out of three standards
    • ITSEC (Information Technology Security Evaluation Criteria)
      • European Standard, developed in early 1990s, by UK, France, the Netherlands, and Germany
    • TCSEC (Trusted Computer System Evaluation Criteria)
      • Widely known as “Orange Book”

Southern Methodist University

history6
History…
  • TCSEC (Trusted Computer System Evaluation Criteria)
    • Issued by United States Government National Computer Security Council, as DoD standard 5200.28-STD, December 1985
  • CTCPEC (Canadian Trusted Computer Product Evaluation Criteria)

Southern Methodist University

history7
History…

First Draft (Version 1.0) was published in January 1996 for comments

  • Version 2.0 was published in 1998, and was accepted by ISO as an Final Committee Draft (FCD) document
  • Version 2.0 became ISO standard sometime in June 1999 with minor, mostly editorial modifications.

Southern Methodist University

history8
History
  • Two versions of CCs were released since then…
    • Version 2.1 was released in August 1999, and now accepted as ISO-15408 standard
    • Version 2.2, the newest version, released this year (2004).

Southern Methodist University

why should we use the cc
Why should we use the CC?
  • What support does CC have?
  • What guarantees do CC-certified/validated products provide?
  • Where should we start, if we want to achieve CC-certificate/validation for our product?

Southern Methodist University

what support does cc have
What support does CC have?..
  • National security and standards organizations within Canada, France, Germany, Netherlands, UK and USA worked in collaboration to replace their existing security evaluation criteria (SEC)

Southern Methodist University

what support does cc have11
What support does CC have?
  • Acceptance by ISO will ensure that CC rapidly becomes the world standard for security specification and evaluation
  • Wider choice for evaluated products for consumers
  • Greater understanding of consumer requirements
  • Greater access to markets for developers

Southern Methodist University

what guarantees products will provide
What guarantees products will provide?
  • A sound basis for confidence that security measures are appropriate to meet a given threat and that they are correctly implemented
  • Quantifies/measures the extent to which security has been assessed
  • Includes an assurance scale, called as Evaluation Assurance Level (EAL)

Southern Methodist University

who could be affected
Who could be affected?

Developers

Vendors

Common

Criteria

Accreditors

Certifiers

Approvers

Evaluators

Consumers

Southern Methodist University

what is cc
What is CC?
  • Overview
  • Building Blocks
    • Security and Functional Requirements
    • Security Assurance Requirements
  • Protection Profiles (PP)
  • Security Targets (ST)

Southern Methodist University

overview
Overview…

Southern Methodist University

overview16
Overview

Southern Methodist University

building blocks
Building Blocks…
  • Security Functional Requirements
    • Grouped into 11 classes
    • Members of each class shares common focus, but differ in emphasis
      • Audit, Cryptographic Support, Communication, User Data Protection, Identification and Authentication, Security Management, Privacy, Protection of TOE security functions, Resource Utilization, TOE Access, Trusted Path/Channels

Southern Methodist University

building blocks18
Building Blocks
    • Audit class contains 6 families dealing with various aspects of auditing
      • data generation, analysis, event storage etc.
  • Each family contains one or more components
    • Audit data generation has 2 components
      • 1 dealing with generation of audit records
      • 2 dealing with association of user with auditable event

Southern Methodist University

security assurance requirements
Security Assurance Requirements…
  • Grouped into Classes  Families  Components
  • In all 8 basic classes and two special classes for PPs and STs
    • Configuration Management, Guidance Documents, Vulnerability Assessment, Delivery and Operation, Life Cycle Support, Assurance Maintenance, Development, Tests

Southern Methodist University

security assurance requirements20
Security Assurance Requirements…
  • Provides 7 predefined assurance packages
  • Known as Evaluation Assurance Levels (EAL)
  • Raising scale of assurance
    • From EAL1 to EAL7

Southern Methodist University

security assurance requirements21
Security Assurance Requirements…
  • EAL1: Functionally Tested
    • Provides evaluation of product as made available to user
    • Independent testing against specification
    • Examination of guidance documents
  • EAL2: Structurally Tested
    • Applicable where developer/user need low  moderate level of assurance
      • For example, legacy systems
  • EAL3: Methodically Tested and Checked
    • Provides analysis supported by “gray box” testing
    • Selective confirmation of test results

Southern Methodist University

security assurance requirements22
Security Assurance Requirements…
  • EAL4: Methodically Designed, Tested and Reviewed
    • Low level analysis of design, and subset of implementation
    • Independent search for vulnerability
  • EAL5: Semi-formally Designed and Testes
    • Analysis of complete implementation
    • Supplemented by formal model
    • Semiformal presentation of functional model, and high level design
    • Search for vulnerability must ensure resistance etc

Southern Methodist University

security assurance requirements23
Security Assurance Requirements
  • EAL6: Semi-formally Verified design and Tested
    • Analysis with modular and layered approach to design and implementation
    • Plus EAL5 and lower level testing
  • EAL7: Formally Verified design and Tested
    • Evaluation of formal model with,
    • formal presentation of formal specification
    • Evidence of “white-box” testing

Southern Methodist University

protection profiles
Protection Profiles…
  • What is Protection Profile?
    • Essentially an implementation independent statement of security requirements that is shown to address threats that exists in a specified environment

Southern Methodist University

protection profiles25
Protection Profiles…

What it contains?

Introduction  PP Identification, PP Overview

TOE Description

TOE Security Environment  Assumptions, Threats, Organizational Security Policies

Security Objectives  For TOE, For Environment

IT Security Requirements  TOE Security Requirements Functional

Assurance

 Security Requirements for IT environment

PP Application Notes

Rationale  Objectives, Requirements

Southern Methodist University

protection profiles26
Protection Profiles
  • When would you want a PP?
    • When setting standards for particular product type
      • A government wishes to specify security requirements for a class of security products, like firewalls, etc.
      • Or, a firm needs an IT system that addresses its security issues

Southern Methodist University

security targets
Security Targets…
  • What is Security Target?
    • A basis against which evaluation is performed
    • Contains security threats, objectives, requirements, summary specification of functions and assurance measures
  • When is ST Needed?
    • When submitting product for evaluation

Southern Methodist University

security targets28
Security Targets…

What are the contents of ST Document?

Introduction  ST Identification, ST Overview, CC conformance

TOE Description

TOE Environment  Assumptions, Threats, Organizational Security Policies

Security Objectives  For TOE, For environment

IT Security Requirements  TOE Security Requirements  Functional, Assurance

 Security Requirements for IT environment

TOE Summary Specification TOE Security Function, Assurance Measures

PP Claims  PP Reference, PP Refinement, Additions

Rationale Security Objective Rationale

Security Requirements Rationale

TOE Summary Specification

PP Claims Rationale

Southern Methodist University

reference
Reference
  • http://csrc.nist.gov/cc/

Southern Methodist University

questions
Questions!!!

Southern Methodist University