CCEVS Public Interpretation Database by Stage

• About the Database

• About the NIAP Interpretations Board (NIB)

• Labeling Convention In NIAP Interpretations

Quickfinder:

• Stage 425: External Post in Interpretations Board Rework
• Stage 460: Ready to Send to Management/CCIMB
• Stage 470: Sent to CCEVS Management and CCIMB for Review
• Stage 480: Submitted as Request for Interpretation/Editorial Observation to CCIMB
• Stage 510: Approved by CCEVS Management and Mailed to Public Mailing List
• Stage 520: Formally Superseded
• Stage 530: Formally Rescinded
• Stage 540: In CCIMB RI Queue
• Stage 550: Approved, Acceptable to CCIMB, No CCIMB Interpretation
• Stage 555: Approved, Acceptable to CCIMB, CCIMB Interpretation Pending
• Stage 600: Withdrawn
• Stage 610: Tabled
• Stage 630: Pending on: APE/ASE Rewrite
• Stage 631: Pending on: ADV Rewrite
• Stage 632: Pending on: ALC/ADO/AGD Rewrite

Index:

• External Post in Interpretations Board Rework (425)
  • I-0453: TSF And Support Code
    (2004-05-06)
    

• Ready to Send to Management/CCIMB (460)
  • I-0387: Auditing Of Audit Storage Failures
    (2005-02-04)
    
  • I-0471: Objects In The TOE
    (2005-02-04)
    
  • I-0482: Properties Of Default Values For Attributes
    (2005-02-04)
    

• Sent to CCEVS Management and CCIMB for Review (470)
  • I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes
    (2003-03-12)
    
  • I-0388: What Is The Difference Between "Sort" And "Order"?
    (2004-03-08)
    
  • I-0392: AVA_MSU Does Not Mandate Extra Functions In The TOE
    (2003-03-12)
    
  • I-0433: Design Abstractions For Non-IT Mechanisms
    (2004-03-08)
    
  • I-0434: Treatment Of TSF Components Provided By A Third-Party
    (2004-03-08)
    
  • I-0436: Compliance Claims Against A Flawed PP
    (2003-08-01)
    
  • I-0440: Clarification Of Detection/Prevention For FIA_UAU.3
    (2004-03-08)
    
  • I-0442: Restrictive Is Not Fully Defined Without Specification Of Attributes
    (2004-01-12)
    
  • I-0451: When To Use IFF/IFC And ACF/ACC
    (2004-03-08)
    
  • I-0461: Definition Of TSF: Relied Upon For The Correct Enforcement
    (2003-08-01)
    
  • I-0463: Platform Inclusion In A TOE With FPT_SEP
    (2003-03-12)
    
  • I-0467: Can Guidance Documentation Meet TSF Requirements?
    (2003-08-01)
    
  • I-0468: Must Test Setup And Cleanup Code Run Unprivileged?
    (2004-11-09)
    
  • I-0469: What Does "Initial Startup" Mean For FPT_AMT And FPT_TST?
    (2004-11-09)
    
  • I-0470: FPT_AMT When There Are No Operational (IT) Environment Objectives
    (2003-08-01)
    
  • I-0472: Correction Of Definition Of Lattice
    (2004-01-12)
    
  • I-0473: Ability To Obtain The Unique Identifier Of The TOE
    (2004-05-06)
    
  • I-0477: Management Of Subject Attributes
    (2004-11-09)
    
  • I-0479: FTP_ITC.1.3 Specifies The Functions Needing A Trusted Channel
    (2004-11-09)
    

• Submitted as Request for Interpretation/Editorial Observation to CCIMB (480)
  • I-0464: Conditional Requirements
    (2004-05-06)
    

• Approved by CCEVS Management and Mailed to Public Mailing List (510)
  • I-0350: Clarification Of Resources/Objects For Residual Information Protection
    (2002-03-04)
    
  • I-0375: Elements Requiring Authentication Mechanism
    (2001-03-15)
    
  • I-0410: Auditing Of Subject Identity For Unsuccessful Logins
    (2002-01-04)
    
  • I-0420: Attribute Inheritance/Modification Rules Need To Be Included In Policy
    (2002-08-22)
    
  • I-0427: Identification Of Standards
    (2001-06-22)
    

• Formally Superseded (520)
  • I-0338: Configuration Items In The Absence Of Explicit Scope
    (Approved 2000-03-27; Superseded 2001-06-22)
    
  • I-0348: Audit Data Loss Prevention Method May Be Site-Selectable
    (Approved 2000-03-27; Superseded 2002-03-11)
    
  • I-0351: User Attributes To Be Bound Should Be Specified
    (Approved 2000-03-27; Superseded 2002-05-14)
    
  • I-0352: Rules Governing Binding Should Be Specifiable
    (Approved 2000-12-20; Superseded 2004-01-30)
    
  • I-0353: Association Of Access Control Attributes With Subjects And Objects
    (Approved 2000-03-27; Superseded 2000-12-05)
    
  • I-0354: Association Of Information Flow Attributes W/Subjects And Information
    (Approved 2000-03-27; Superseded 2000-12-11)
    
  • I-0355: Evaluation Of The TOE Summary Specification: Part 1 Vs Part 3
    (Approved 2000-03-27; Superseded 2000-12-05)
    
  • I-0362: Scope Of Permitted Refinements
    (Approved 2000-03-27; Superseded 2002-03-12)
    
  • I-0363: Attribute Inheritance/Modification Rules Need To Be Included In Policy
    (Approved 2000-03-27; Superseded 2002-08-22)
    
  • I-0364: Application Notes In Protection Profiles Are Informative Only
    (Approved 2000-03-27; Superseded 2001-06-22)
    
  • I-0370: Clarification Of ``Audit Records''
    (Approved 2000-03-27; Superseded 2000-12-05)
    
  • I-0371: Some Modifications To The Audit Trail Are Authorized
    (Approved 2000-03-27; Superseded 2000-12-11)
    
  • I-0373: FPT_SEP.2 And FPT_SEP.3 Are Not Hierarchical
    (Approved 2000-03-27; Superseded 2000-12-05)
    
  • I-0377: Settable Failure Limits Are Permitted
    (Approved 2000-03-27; Superseded 2000-12-05)
    
  • I-0381: Relationship Between FPT_PHP And FMT_MOF
    (Approved 2002-03-04; Superseded 2003-10-31)
    
  • I-0383: Content Of PP Claims Rationale
    (Approved 2000-03-27; Superseded 2000-12-05)
    
  • I-0385: Identification Of Standards
    (Approved 2000-03-27; Superseded 2001-06-22)
    
  • I-0393: A Completely Evaluated ST Is Not Required When TOE Evaluation Starts
    (Approved 2001-03-15; Superseded 2003-07-15)
    
  • I-0394: Iteration Must Cover All Scopes
    (Approved 2000-12-20; Superseded 2002-03-12)
    
  • I-0395: Security Attributes Include Attributes Of Information And Resources
    (Approved 2001-03-15; Superseded 2003-10-31)
    
  • I-0397: Iteration On Assurance Components/Elements
    (Approved 2001-03-15; Superseded 2002-03-12)
    
  • I-0406: Automated Or Manual Recovery Is Acceptable
    (Approved 2001-03-15; Superseded 2003-10-31)
    
  • I-0409: Other Properties In FMT_MSA.3 Should Be Specified By Assignment
    (Approved 2002-01-04; Superseded 2003-10-31)
    
  • I-0411: Guidance Includes AGD_ADM, AGD_USR, ADO, And ALC_FLR
    (Approved 2000-12-22; Superseded 2003-07-15)
    
  • I-0412: Configuration Items In The Absence Of Configuration Management
    (Approved 2001-06-22; Superseded 2003-05-09)
    
  • I-0415: User Attributes To Be Bound Should Be Specified
    (Approved 2002-03-04; Superseded 2004-01-30)
    
  • I-0416: Association Of Access Control Attributes With Subjects And Objects
    (Approved 2000-12-05; Superseded 2003-07-15)
    
  • I-0417: Association Of Information Flow Attributes W/Subjects And Information
    (Approved 2000-12-11; Superseded 2003-07-15)
    
  • I-0423: Some Modifications To The Audit Trail Are Authorized
    (Approved 2000-12-11; Superseded 2003-07-15)
    
  • I-0425: Settable Failure Limits Are Permitted
    (Approved 2000-12-05; Superseded 2003-10-31)
    

• Formally Rescinded (530)
  • I-0339: Assurance Of RVM Is By Testing And Design Analysis
    (Approved 2000-03-27; Rescinded 2002-01-04)
    
  • I-0389: Recovery To A Known State
    (Approved 2001-03-15; Rescinded 2003-05-09)
    
  • I-0424: FPT_SEP.2 And FPT_SEP.3 Are Not Hierarchical
    (Approved 2000-12-05; Rescinded 2003-05-09)
    

• In CCIMB RI Queue (540)
  • I-0367: Management Sections Are Informative
    (2003-05-15)
    
  • I-0378: Meaning Of Compliance Claims
    (2003-05-15)
    
  • I-0379: How To Require User/Admin Documentation For Functional Components
    (2003-05-15)
    
  • I-0382: TSF Architectural Protections Are Really Assurances
    (2003-05-15)
    

• Approved, Acceptable to CCIMB, No CCIMB Interpretation (550)
  • I-0347: Including Sensitive Information In Audit Records
    (2003-07-17)
    
  • I-0405: American English Is An Acceptable Refinement
    (2003-08-01)
    
  • I-0407: Empty Selections Or Assignments
    (2003-08-21)
    
  • I-0414: Site-Configurable Prevention Of Audit Loss
    (2003-07-17)
    
  • I-0421: Application Notes In Protection Profiles Are Informative Only
    (2003-08-21)
    
  • I-0422: Clarification Of ``Audit Records''
    (2003-07-17)
    
  • I-0429: Selecting One Or More
    (2003-08-12)
    
  • I-0432: List Of Subjects And Objects Refers To Types Thereof
    (2004-01-30)
    

• Approved, Acceptable to CCIMB, CCIMB Interpretation Pending (555)
  • I-0418: Evaluation Of The TOE Summary Specification: Part 1 Vs Part 3
    (2003-11-11)
    
  • I-0426: Content Of PP Claims Rationale
    (2003-07-17)
    
  • I-0459: CM Systems May Have Varying Degrees Of Rigor And Function
    (2003-07-17)
    

• Withdrawn (600)
  • I-0346: Users Authorised To Change Authentication Data Are Not Roles
    (1999-11-04)
    
  • I-0349: Grammatical/Typographical Corrections In Common Criteria V2.1
    (2004-11-03)
    
  • I-0358: Roles Whose Membership Is Defined By Object Attributes
    (1999-12-17)
    
  • I-0359: Ordering Of Basic And Minimal Audit For FMT_REV
    (1999-11-04)
    
  • I-0361: "Reference" Refers To A Citation Of The Text Source
    (2000-03-21)
    
  • I-0369: Security Management Functions To Be Provided Must Be Enumerated
    (2001-08-28)
    
  • I-0372: Audit Records Must Be Protected At All Times
    (2001-11-15)
    
  • I-0374: Nature Of Components
    (2001-06-14)
    
  • I-0376: Dependencies Between FIA_UID And FIA_ATD
    (1999-10-01)
    
  • I-0390: Clarification Of Implied Evaluation Actions For CM
    (2003-02-11)
    
  • I-0391: Missing Mapping: IT Environment Requirements And High-Level Design
    (2003-05-12)
    
  • I-0396: Application Notes Are Permitted In Security Targets
    (2000-06-06)
    
  • I-0400: Focus Is On Content, Not Structure, For AMA
    (2004-05-06)
    
  • I-0401: Clarify Use Of Component Categorization Report
    (2004-05-06)
    
  • I-0402: Identification Of The Certified Version
    (2004-05-06)
    
  • I-0413: Assurance Of RVM Is By Testing And Design Analysis
    (2001-04-23)
    
  • I-0419: Scope Of Permitted Refinements
    (2002-03-12)
    
  • I-0428: National Interpretations Do Not Require SRE Evaluation
    (2004-05-06)
    
  • I-0430: When Are SOF Claims Required?
    (2002-03-12)
    
  • I-0431: Specification Of Explicitly Specified Requirements
    (2003-05-12)
    
  • I-0441: Meaning Of "Other Property"
    (2001-08-28)
    
  • I-0443: Minor (Non-Substantive) Corrections To The CC And CEM
    (2004-11-03)
    
  • I-0446: CEM For Either No SEP Or No RVM
    (2004-05-06)
    
  • I-0449: Flexibility In Meeting Requirements
    (2003-05-12)
    
  • I-0457: Interfaces To Be Examined For ADV_FSP
    (2004-02-24)
    
  • I-0460: Empty Selections Or Assignments/One Or More
    (2004-02-24)
    
  • I-0462: What Is A TSP?
    (2004-05-06)
    
  • I-0481: Ignoring Events Is Incompatible With Preventing Audit Loss
    (2005-02-04)
    

• Tabled (610)
  • I-0365: Broad Consistency And Coherency Of Application Notes In A PP
    (1999-12-17)
    
  • I-0399: Flaw Remediation Is Independent Of Maintenance Of Assurance
    (2000-07-12)
    
  • I-0438: Lack Of Integration Guidance
    (2002-01-14)
    
  • I-0480: Components Written As Environmental Actions
    (2005-02-04)
    

• Pending on: APE/ASE Rewrite (630)
  • I-0360: Non-Normative Materials In Annexes B (PP) And C (ST)
    (2004-05-07)
    
  • I-0368: Assumptions Related To Security Objectives For The Environment
    (2004-05-07)
    
  • I-0398: Assumptions, Objectives, And Environmental Requirements
    (2004-05-07)
    
  • I-0403: Guidance Refinements Must Be Tracable To Objectives
    (2004-05-07)
    
  • I-0404: Security Requirements For The Non-IT Environment
    (2004-05-07)
    
  • I-0435: Evaluation Of An ST Compliant With A Previously Evaluated PP
    (2004-05-07)
    
  • I-0437: Applicability Of Elements Of A PP In The ST Context
    (2004-05-07)
    
  • I-0439: PP Compliance And Hierarchical Components
    (2004-05-07)
    
  • I-0444: PP Conformance Claims To The CC
    (2004-05-07)
    
  • I-0447: Level Of Detail For The TSS
    (2004-05-07)
    
  • I-0448: Required Level Of Detail For Environmental Requirements
    (2004-05-07)
    
  • I-0458: Part 1/Part 3 Disconnect: How Something Is Implemented
    (2004-05-07)
    

• Pending on: ADV Rewrite (631)
  • I-0380: FPT_ITT, FPT_SSP, And FPT_TRC Should Be Incorporated Into FPT_SEP
    (2004-05-07)
    
  • I-0384: Subsystems Interfaces Are Described At A High Level
    (2004-05-07)
    
  • I-0386: High Level Design Is Too Close To Implementation
    (2004-05-07)
    
  • I-0408: FSP Evaluation Must Consider The Whole TSP
    (2004-05-07)
    
  • I-0445: ADV Class Inadequate
    (2004-05-07)
    
  • I-0450: Appropriate Levels Of Decomposition
    (2004-05-07)
    
  • I-0466: What Is The Difference Between TSF And TOE?
    (2004-05-07)
    

• Pending on: ALC/ADO/AGD Rewrite (632)
  • I-0474: Do ACM And ALC Apply To The TOE Or The TSF?
    (2004-05-07)
    

Return to Index Selection Page

This page was generated on Fri Jun 30 12:32:35 2006.
Questions on this page, or comments on Database entries should be addressed to cc-cmt@nist.gov.
Flags are based on a comparison against information uploaded 2005-01-20-00:00