cc-cmt@nist.gov Mail Index (by Thread)

• Date Index

• PD 0150: FTA_SSL.1 and 2 SFRs in the Firewall, Traffic Filter Firewall, VPN, and IDS MR PPs, Observation Decisions Review Board
• PD 0151: Acceptable Demonstrable Assurance for the IDS System PP v1.7 (BR), Observation Decisions Review Board
• PD 0152: Internal Inconsistency within the IDS System PP regarding FPT_STM, Observation Decisions Review Board
• Lost Laptop PP, Nir Naaman
• PD 0149: Clarification of FMT_MOF.1(3) for TFWPP and VPNPPs, Observation Decisions Review Board
  • RE: PD 0149: Clarification of FMT_MOF.1(3) for TFWPP and VPNPPs, Alex Ragen
• PD 0147: CCEVS Policy #15 Applicability to Flash Drives, Observation Decisions Review Board
• Re: TSFI Determination, Observation Decisions Review Board
• PD 0148: Excluded Functionality and Policy 13, Observation Decisions Review Board
• Correction to PD 143, Observation Decisions Review Board
• PD 0146: Remote Administration and Cryptographic Functionality in the TFWPP, Observation Decisions Review Board
• PD 0143: Meeting FTA_TAH_EXP.1 in the DBMS PP, Observation Decisions Review Board
  • TSFI Determination, Arnold, James L. Jr.
    • RE: TSFI Determination, Mike Boberski
    • RE: TSFI Determination, Nir Naaman
• PD 0145: Enabling/Disabling of Verification of Cryptographic Key Testing in WLAN PP, Observation Decisions Review Board
• PD 0144: Corrections to formatting and typographic errors in the WLAN Access System PPs, Observation Decisions Review Board
• PD 0142: Meeting FTA_TAH_EXP.1 in the DBMS PP, Observation Decisions Review Board
• Re: Clarification/Correction on CC v3.1 ADV_TDS.3, Observation Decisions Review Board
  • RE: Clarification/Correction on CC v3.1 ADV_TDS.3, Michelle Ruppel
• CC v4 ideas and suggestions, Nir Naaman
• PD 0140: Clarification on conformance to consistency issues noted in the U.S. Government Wireless Local Area Network (WLAN) Cli, Observation Decisions Review Board
  • Re: PD 0140: Clarification on conformance to consistency issues noted in the U.S. Government Wireless Local Area Network (WLAN) Cli, holt
• Re: PD 0135: "Overwriting" in the Context of Non-Disk Memory (Medium Robustness Profiles), Observation Decisions Review Board
  • RE: PD 0135: "Overwriting" in the Context of Non-Disk Memory (Medium Robustness Profiles), Dill, Ken
    • RE: PD 0135: "Overwriting" in the Context of Non-Disk Memory (Medium Robustness Profiles), Daniel P. Faigin
• PD 0141: OD 0265: Clarification on conformance to consistency issues noted in the U.S. Government Wireless Local Area Network (, Observation Decisions Review Board
  • Re: PD 0141: OD 0265: Clarification on conformance to consistency issues noted in the U.S. Government Wireless Local Area Network (, david
  • Re: PD 0141: OD 0265: Clarification on conformance to consistency issues noted in the U.S. Government Wireless Local Area Network (, gordon
• PD 0138: Sharing of Peripherals with Memory under the Peripheral Sharing PP, Observation Decisions Review Board
• PD 0136: Using CCv2.x PPs with CCv3.1 STs: Handling of FPT_SEP and FPT_RVM, Observation Decisions Review Board
• Re: FDP_ITT.4 Attribute-based integrity monitoring, NIAP Interpretations Board
• PD 0139: CC V3 Conformance Type for Existing CC V2 PPs, Observation Decisions Review Board
• PD 0137: CC V3 PP Conformance Type Consistency, Observation Decisions Review Board
• Updated PD 0097: Compliance with IDS System PP Export Requirements, Observation Decisions Review Board
• Re: Addendum to Policy Letter 13: Audit Generation Functionality, Observation Decisions Review Board
• PD 0135: "Overwriting" in the Context of Flash Memory (Medium Robustness, Observation Decisions Review Board
• PD 0134: Medium Robustness Traffic Filtering PP: Administrator accounts, Observation Decisions Review Board
• PD 0133: Level of Detail in SFRs, Observation Decisions Review Board
  • RE: PD 0133: Level of Detail in SFRs, Arnold, James L. Jr.
  • RE: PD 0133: Level of Detail in SFRs, Arnold, James L. Jr.
    • RE: PD 0133: Level of Detail in SFRs, Stoneburner, Gary R.
      • RE: PD 0133: Level of Detail in SFRs, Arnold, James L. Jr.
  • Re: PD 0133: Level of Detail in SFRs, Observation Decisions Review Board
• Re: Type Correction (PD-0112), Observation Decisions Review Board
• PD 0131: Create Object Audit Event and CAPP Compliance, Observation Decisions Review Board
  • RE: PD 0131: Create Object Audit Event and CAPP Compliance, Arnold, James L. Jr.
    • Re: PD 0131: Create Object Audit Event and CAPP Compliance, Helmut Kurth
      • RE: PD 0131: Create Object Audit Event and CAPP Compliance, Nir Naaman
      • Re: PD 0131: Create Object Audit Event and CAPP Compliance, YOKOTA HIROFUMI
      • Re: PD 0131: Create Object Audit Event and CAPP Compliance, YOKOTA HIROFUMI
      • RE: PD 0131: Create Object Audit Event and CAPP Compliance, Stoneburner, Gary R.
      • RE: PD 0131: Create Object Audit Event and CAPP Compliance, Boberski, Michael A.
      • RE: PD 0131: Create Object Audit Event and CAPP Compliance, Stoneburner, Gary R.
      • Re: PD 0131: Create Object Audit Event and CAPP Compliance, Olin Sibert
      • Addendum to Policy Letter 13: Audit Generation Functionality, Arnold, James L. Jr.
      • Re: Addendum to Policy Letter 13: Audit Generation Functionality, Hal W Forsberg
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Michelle Ruppel
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Dawn Adams
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Daniel P. Faigin
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Stoneburner, Gary R.
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Hal W Forsberg
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Daniel P. Faigin
      • Addendum to Policy Letter 13: Audit Generation Functionality, Daniel P. Faigin
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Stoneburner, Gary R.
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Daniel P. Faigin
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Williamson, Robert L. Jr.
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Daniel P. Faigin
      • RE: Addendum to Policy Letter 13: Audit Generation Functionality, Michelle Ruppel
  • Re: PD 0131: Create Object Audit Event and CAPP Compliance, Observation Decisions Review Board
• PD 0132: Terminating Sessions in lieu of Locking Sessions, Observation Decisions Review Board
• Re: PD 0130:Clarification of Alert requirement in Basic Robustness, Observation Decisions Review Board
• RE: SFRs - Requirement Specification or Implementation Descripti on?, Kris Rogers
  • RE: SFRs - Requirement Specification or Implementation Descripti on?, Arnold, James L. Jr.
    • RE: SFRs - Requirement Specification or Implementation Descripti on?, Nir Naaman
• SFRs - Requirement Specification or Implementation Description?, Apted, Tony J. [RA]
  • Re: SFRs - Requirement Specification or Implementation Description?, Helmut Kurth
  • RE: SFRs - Requirement Specification or Implementation Description?, Stoneburner, Gary R.
  • RE: SFRs - Requirement Specification or Implementation Description?, Nir Naaman
  • Re: SFRs - Requirement Specification or Implementation Description?, YOKOTA HIROFUMI
  • RE: SFRs - Requirement Specification or Implementation Description?, Squires, Alicia
    • Re: SFRs - Requirement Specification or Implementation Description?, Dirk-Jan Out
      • Re: SFRs - Requirement Specification or Implementation Description?, YOKOTA HIROFUMI
      • Re: SFRs - Requirement Specification or Implementation Description?, YOKOTA HIROFUMI
      • Re: SFRs - Requirement Specification or Implementation Description?, YOKOTA HIROFUMI
      • RE: SFRs - Requirement Specification or Implementation Description?, Nir Naaman
      • RE: SFRs - Requirement Specification or Implementation Description?, John Boone
    • type correction (PD-0112), YOKOTA HIROFUMI
      • Re: type correction (PD-0112), Hal W Forsberg
      • Re: type correction (PD-0112), Hal W Forsberg
      • Re: type correction (PD-0112), YOKOTA HIROFUMI
  • Re: SFRs - Requirement Specification or Implementation Description?, Tom Benkart
    • Re: SFRs - Requirement Specification or Implementation Description?, Dirk-Jan Out
• Re: Acceptance plan needed for configuration items that don't go into the TOE, Observation Decisions Review Board
• PD 0130:Clarification of Alert requirement in Basic Robustness Anti-Virus PP, Observation Decisions Review Board
• PD 0128: Information in Test Results for Manual Tests, Observation Decisions Review Board
• PD 0129: Deletion of the oldest audit events when audit storage space is exhausted, Observation Decisions Review Board
  • Re: PD 0129: Deletion of the oldest audit events when audit storage space is exhausted, YOKOTA HIROFUMI
    • MAC and DAC and the combination, YOKOTA HIROFUMI
      • RE: MAC and DAC and the combination, Boberski, Michael A.
      • RE: MAC and DAC and the combination, Nir Naaman
      • Re: MAC and DAC and the combination, YOKOTA HIROFUMI
  • Re: PD 0129: Deletion of the oldest audit events when audit storage space is exhausted, Observation Decisions Review Board
• RE: wordings are not consistent in CCV3.1, Stoneburner, Gary R.
  • Re: Wordings are not consistent in CCV3.1, NIAP Interpretations Board
• CCEVS Announcement Impact, Kathy Shonaiya
  • RE: CCEVS Announcement Impact, Stoneburner, Gary R.
  • RE: CCEVS Announcement Impact, Stoneburner, Gary R.
• The meaning of "not otherwise described", YOKOTA HIROFUMI
  • RE: The meaning of "not otherwise described", Stoneburner, Gary R.
  • Re: The meaning of "not otherwise described", NIAP Interpretations Board
  • Re: The meaning of "not otherwise described", Observation Decisions Review Board
  • Re: Re: The meaning of "not otherwise described", gordon
  • Re: Re: The meaning of "not otherwise described", klaus
• Update on CCv3, Observation Decisions Review Board
  • Clarification/Correction on CC v3.1 ADV_TDS.3, Michelle Ruppel
  • RE: Clarification/Correction on CC v3.1 ADV_TDS.3, Michelle Ruppel
    • Message not available
      • RE: Clarification/Correction on CC v3.1 ADV_TDS.3, Michelle Ruppel
• PD 0127: Compliance with IDS Analyzer PP Export Requirements, Observation Decisions Review Board
• Re: Installation, generation and start-up vs. implementation/PD 0126: Administrator-entered Code Used To Meet SFRs, Observation Decisions Review Board
• Re: TSS Level of Detail/PD 0063: What Information Must Be Provided in the TSS, Observation Decisions Review Board
  • RE: TSS Level of Detail/PD 0063: What Information Must Be Provided in the TSS, Alex Ragen
    • RE: TSS Level of Detail/PD 0063: What Information Must Be Provided in the TSS, Daniel P. Faigin
      • Re: TSS Level of Detail/PD 0063: What Information Must Be Provided in the TSS, YOKOTA HIROFUMI
      • wordings are not consistent in CCV3.1, YOKOTA HIROFUMI
      • Re: wordings are not consistent in CCV3.1, Dirk-Jan Out
      • Re: wordings are not consistent in CCV3.1, YOKOTA HIROFUMI
      • RE: wordings are not consistent in CCV3.1, John Boone
      • Re: wordings are not consistent in CCV3.1, YOKOTA HIROFUMI
      • RE: wordings are not consistent in CCV3.1, John Boone
      • FDP_ITT.4 Attribute-based integrity monitoring, YOKOTA HIROFUMI
      • Re: FDP_ITT.4 Attribute-based integrity monitoring, YOKOTA HIROFUMI
      • RE: TSS Level of Detail/PD 0063: What Information Must Be Provided in the TSS, YOKOTA HIROFUMI
  • Re: TSS Level of Detail/PD 0063: What Information Must Be Provided in the TSS, YOKOTA HIROFUMI
• HLD and IT Environment SFRs, Arnold, James L. Jr.
  • Message not available
    • Re: HLD and IT Environment SFRs, Tom Benkart
  • RE: HLD and IT Environment SFRs, John Boone
• A.NO_EVIL for TOE with limited privileges, Michelle Ruppel
  • RE: A.NO_EVIL for TOE with limited privileges, John Boone
    • RE: A.NO_EVIL for TOE with limited privileges, Alex Ragen
      • Re: A.NO_EVIL for TOE with limited privileges, Richie
      • RE: A.NO_EVIL for TOE with limited privileges, John Boone
      • RE: A.NO_EVIL for TOE with limited privileges, Michelle Ruppel
  • RE: A.NO_EVIL for TOE with limited privileges, Nir Naaman
    • Re: A.NO_EVIL for TOE with limited privileges, YOKOTA HIROFUMI
      • Re: A.NO_EVIL for TOE with limited privileges, Dirk-Jan Out
      • RE: A.NO_EVIL for TOE with limited privileges, Alex Ragen
      • RE: A.NO_EVIL for TOE with limited privileges, John Boone
      • Re: A.NO_EVIL for TOE with limited privileges, Richard Tiernan
      • RE: A.NO_EVIL for TOE with limited privileges, John Boone
      • RE: A.NO_EVIL for TOE with limited privileges, Nir Naaman
      • Re: A.NO_EVIL for TOE with limited privileges, YOKOTA HIROFUMI
      • Re: A.NO_EVIL for TOE with limited privileges, YOKOTA HIROFUMI
  • RE: A.NO_EVIL for TOE with limited privileges, Stoneburner, Gary R.
  • Re: A.NO_EVIL for TOE with limited privileges, Observation Decisions Review Board
• Browser in the TOE for web-based administration?, Michelle Ruppel
  • RE: Browser in the TOE for web-based administration?, Boberski, Michael A.
    • Re: Browser in the TOE for web-based administration?, out
      • Re: Browser in the TOE for web-based administration?, Richie
      • Re: Browser in the TOE for web-based administration?, Dirk-Jan Out
  • RE: Browser in the TOE for web-based administration?, Stoneburner, Gary R.
  • RE: Browser in the TOE for web-based administration?, Boberski, Michael A.
  • RE: Browser in the TOE for web-based administration?, Stoneburner, Gary R.
  • RE: Browser in the TOE for web-based administration?, Boberski, Michael A.
  • Re: Browser in the TOE for web-based administration?, Observation Decisions Review Board
• Interfaces in the Logical Boundary, Michelle Ruppel
  • Re: Interfaces in the Logical Boundary, Observation Decisions Review Board
• Fw: [CORRECTION] Critical Infrastructure Protection ma, Bob Radvanovsky
• ACM_SCP V2.2 vs ALC_CMS V3.0, Alexandre le Goaster
  • Re: ACM_SCP V2.2 vs ALC_CMS V3.0, Observation Decisions Review Board
• FDP_UCT description wrong in CC Part 2 Section 6.12, Michelle Ruppel
  • Re: FDP_UCT description wrong in CC Part 2 Section 6.12, Observation Decisions Review Board
• Typo in CC Part 2 v2.3 with FPT_TST.1.1, Tom Benkart
  • Re: Typo in CC Part 2 v2.3 with FPT_TST.1.1, Observation Decisions Review Board
    • Acceptance plan needed for configuration items that don't go into the TOE, Ben Rogers
• [ANNOUNCEMENT] Mailing list relating to CRITICAL INFRASTRUCTURE PROTECTION, Bob Radvanovsky
• Classification in CC V3.0, Alexandre le Goaster
  • Re: Classification in CC V3.0, Observation Decisions Review Board
    • Re: Classification in CC V3.0, Alexandre le Goaster
• V2.2 --> V3.0... i'm lost..., Alexandre le Goaster
• FMT in CC V3.0, Michelle Ruppel
• Resaonableness (was part of RE: PD 0126: Administrator-entered Code Used To Meet SFRs), Stoneburner, Gary R.
• PD 0126: Administrator-entered Code Used To Meet SFRs, Observation Decisions Review Board
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Magosányi Árpád
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Boberski, Michael A.
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Nir Naaman
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Olin Sibert
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Nir Naaman
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Nir Naaman
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Olin Sibert
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Nir Naaman
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Magosányi Árpád
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Nir Naaman
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Olin Sibert
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Nir Naaman
      • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Trey Henefield
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Williamson, Robert L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
    • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Daniel P. Faigin
  • RE: PD 0126: Administrator-entered Code Used To Meet SFRs, Arnold, James L. Jr.
• PD 0063: What Information Must Be Provided in the TSS, Observation Decisions Review Board
  • RE: PD 0063: What Information Must Be Provided in the TSS, Arnold, James L. Jr.
    • Re: PD 0063: What Information Must Be Provided in the TSS, Dirk-Jan Out
  • RE: PD 0063: What Information Must Be Provided in the TSS, Boberski, Michael A.
  • RE: PD 0063: What Information Must Be Provided in the TSS, Arnold, James L. Jr.
    • RE: PD 0063: What Information Must Be Provided in the TSS, Daniel P. Faigin
      • RE: PD 0063: What Information Must Be Provided in the TSS, Hal W Forsberg
  • RE: PD 0063: What Information Must Be Provided in the TSS, Arnold, James L. Jr.
    • RE: PD 0063: What Information Must Be Provided in the TSS, Daniel P. Faigin
      • RE: PD 0063: What Information Must Be Provided in the TSS, Daniel P. Faigin
    • Re: PD 0063: What Information Must Be Provided in the TSS, Dirk-Jan Out
      • Re: PD 0063: What Information Must Be Provided in the TSS, Daniel P. Faigin
  • RE: PD 0063: What Information Must Be Provided in the TSS, Apted, Tony J. [RA]
    • RE: PD 0063: What Information Must Be Provided in the TSS, Nir Naaman
      • RE: PD 0063: What Information Must Be Provided in the TSS, Daniel P. Faigin
• TSS Level of Detail, Arnold, James L. Jr.
  • TSS Level of Detail, Daniel P. Faigin
  • RE: TSS Level of Detail, Trey Henefield
  • RE: TSS Level of Detail, Williamson, Robert L. Jr.
  • RE: TSS Level of Detail, Williamson, Robert L. Jr.
    • RE: TSS Level of Detail, Daniel P. Faigin
• Installation, generation and start-up vs. implementation, Arnold, James L. Jr.
  • Installation, generation and start-up vs. implementation, Daniel P. Faigin
  • RE: Installation, generation and start-up vs. implementation, Trey Henefield
    • RE: Installation, generation and start-up vs. implementation, Daniel P. Faigin
      • RE: Installation, generation and start-up vs. implementation, Trey Henefield
  • RE: Installation, generation and start-up vs. implementation, Nir Naaman
  • RE: Installation, generation and start-up vs. implementation, Williamson, Robert L. Jr.
  • RE: Installation, generation and start-up vs. implementation, Arnold, James L. Jr.
  • RE: Installation, generation and start-up vs. implementation, Arnold, James L. Jr.
• FDP_ITC and signature decryption, Richard Relph
  • Re: FDP_ITC and signature decryption, Helmut Kurth
• semiformal vs informal, Stoneburner, Gary R.
• Updated PD 0124: Depth of Protocol or Interface Examination, Observation Decisions Review Board
  • RE: Updated PD 0124: Depth of Protocol or Interface Examination, Stoneburner, Gary R.
  • Re: Updated PD 0124: Depth of Protocol or Interface Examination, Observation Decisions Review Board
• Re: PD 0113: Use of Third-party Security Mechanisms in TOE, Observation Decisions Review Board
• PD -0125: Audit Pre-Selection in the CIMC PP, Observation Decisions Review Board
• Sad News, Daniel P. Faigin
• Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Greg Bremen
  • RE: CCv3.0 STs claiming conformance to CCv2.2 PPs, Nir Naaman
• CC v3.0 draft - ADV_ARC.1, Stoneburner, Gary R.
  • RE: CC v3.0 draft - ADV_ARC.1, Nir Naaman
    • CCv3.0 STs claiming conformance to CCv2.2 PPs, Nir Naaman
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Dirk-Jan Out
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Helmut Kurth
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Dirk-Jan Out
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Helmut Kurth
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Dirk-Jan Out
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Daniel P. Faigin
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Helmut Kurth
      • Re: CCv3.0 STs claiming conformance to CCv2.2 PPs, Daniel P. Faigin
• PD 0120: Parameter Validation Testing, Observation Decisions Review Board
• PD 0123: Defining Protocols as Internal or External Interfaces, Observation Decisions Review Board
• PD 0122: Description of Logical and Physical Boundaries, Observation Decisions Review Board
  • RE: PD 0122: Description of Logical and Physical Boundaries, Trey Henefield
    • RE: PD 0122: Description of Logical and Physical Boundaries, Daniel P. Faigin
  • RE: PD 0122: Description of Logical and Physical Boundaries, Michelle Ruppel
  • FW: PD 0122: Description of Logical and Physical Boundaries, Michelle Ruppel
  • RE: PD 0122: Description of Logical and Physical Boundaries, Arnold, James L. Jr.
    • Re: PD 0122: Description of Logical and Physical Boundaries, Dirk-Jan Out
  • RE: PD 0122: Description of Logical and Physical Boundaries, Arnold, James L. Jr.
    • RE: PD 0122: Description of Logical and Physical Boundaries, Daniel P. Faigin
      • Re: PD 0122: Description of Logical and Physical Boundaries, Dirk-Jan Out
      • Re: PD 0122: Description of Logical and Physical Boundaries, Daniel P. Faigin
    • Re: PD 0122: Description of Logical and Physical Boundaries, Dirk-Jan Out
  • RE: PD 0122: Description of Logical and Physical Boundaries, Arnold, James L. Jr.
    • Re: PD 0122: Description of Logical and Physical Boundaries, Dirk-Jan Out
      • RE: PD 0122: Description of Logical and Physical Boundaries, Nir Naaman
  • PD 0122: Description of Logical and Physical Boundaries, YOKOTA HIROFUMI
  • RE: PD 0122: Description of Logical and Physical Boundaries, Williamson, Robert L. Jr.
    • RE: PD 0122: Description of Logical and Physical Boundaries, Daniel P. Faigin
  • Re: PD 0122: Description of Logical and Physical Boundaries, Observation Decisions Review Board
• PD 0124: Depth of Protocol or Interface Examination, Observation Decisions Review Board
  • RE: PD 0124: Depth of Protocol or Interface Examination, Michelle Ruppel
  • RE: PD 0124: Depth of Protocol or Interface Examination, Broom, Ralph A.
    • RE: PD 0124: Depth of Protocol or Interface Examination, Michelle Ruppel
  • Re: PD 0124: Depth of Protocol or Interface Examination, Observation Decisions Review Board
• PD 0113 updated, Observation Decisions Review Board
• PD 0121: Format of the ADV_IMP Implementation Representation, Observation Decisions Review Board
• PD 117 Revised, Observation Decisions Review Board
• PD 0119: Applicability of FIA_UAU.7 Application Note in CAPP v1.d, Observation Decisions Review Board
• RE: TOE unique identifiers for hardware, Stoneburner, Gary R.
  • RE: TOE unique identifiers for hardware, Michelle Ruppel
  • RE: TOE unique identifiers for hardware, Stoneburner, Gary R.
  • Re: TOE unique identifiers for hardware, NIAP Interpretations Board
• New CCIMB Interpretations, NIAP Interpretations Board
• PD 118: Assumptions in the IDS PP v1.4, Observation Decisions Review Board
• PD 0117: PP conformance Using an Underlying Evaluated Product, Observation Decisions Review Board
  • Re: PD 0117: PP conformance Using an Underlying Evaluated Product, Tom Benkart
  • Re: PD 0117: PP conformance Using an Underlying Evaluated Product, Observation Decisions Review Board
• Sorry again - complete response, Hal W Forsberg
  • Re: Sorry again - complete response, Dirk-Jan Out
    • Re: Sorry again - complete response, YOKOTA HIROFUMI
      • Re: Sorry again - complete response, Dirk-Jan Out
      • Re: Sorry again - complete response, YOKOTA HIROFUMI
      • Re: Sorry again - complete response, Dirk-Jan Out
      • Re: Sorry again - complete response, YOKOTA HIROFUMI
  • RE: Sorry again - complete response, Nir Naaman
    • RE: Sorry again - complete response, Hal W Forsberg
  • RE: Sorry again - complete response, Stoneburner, Gary R.
    • RE: Sorry again - complete response, Nir Naaman
  • RE: Sorry again - complete response, Stoneburner, Gary R.
• RE: CC 3.0 draft?, Pamela.Grannum
  • Re: CC 3.0 draft?, Dirk-Jan Out
• ST Opinions/Requirements, Michelle Ruppel
  • Re: ST Opinions/Requirements, Dirk-Jan Out
    • Re: ST Opinions/Requirements, YOKOTA HIROFUMI
  • Re: ST Opinions/Requirements, Hal W Forsberg
  • Re: ST Opinions/Requirements - Continued - Sorry for the pre-send!, Hal W Forsberg
  • Re: ST Opinions/Requirements, NIAP Interpretations Board
• RE: FIA_UID interpretations, Stoneburner, Gary R.
  • RE: FIA_UID interpretations, Apted, Tony J. [RA]
    • RE: FIA_UID interpretations, Michelle A. Ruppel
  • RE: FIA_UID interpretations, Greg Bremen
    • Re: FIA_UID interpretations, Dirk-Jan Out
      • CC 3.0 draft?, fbsnodgr
• How to pronounce ISO15408, YOKOTA HIROFUMI
  • How to pronounce ISO15408, Daniel P. Faigin
  • RE: How to pronounce ISO15408, Foreman, Elizabeth A.
  • RE: How to pronounce ISO15408, Lewis, Alton W
• What is the meaning of "not specified" in FAU_GEN.1.1 (b)?, Tom Benkart
  • RE: What is the meaning of "not specified" in FAU_GEN.1.1 (b)?, Stoneburner, Gary R.
  • RE: What is the meaning of "not specified" in FAU_GEN.1.1 (b)?, Lewis, Alton W
  • RE: What is the meaning of "not specified" in FAU_GEN.1.1 (b)?, Lewis, Alton W
  • RE: What is the meaning of "not specified" in FAU_GEN.1.1 (b)?, Foreman, Elizabeth A.
• PD 0116: IDSSPP v1.4: Compliance with the Selective Audit Requirement, Observation Decisions Review Board
• I-0482: Properties Of Default Values For Attributes, NIAP Interpretations Board
  • Re: I-0482: Properties Of Default Values For Attributes, YOKOTA HIROFUMI
  • Re: I-0482: Properties Of Default Values For Attributes, NIAP Interpretations Board
• I-0471: Objects In The TOE, NIAP Interpretations Board
• Updated PD 0103: Clarify CCEVS Policy for Applying NIAP Interpretations, Observation Decisions Review Board
• PD 0115: Third Party Authentication is permitted by the ALFWPP-MR, Observation Decisions Review Board
• PD 0114: Meeting the ADO_DEL.3 Requirement, Observation Decisions Review Board
• PD 0113: Use of Third-party Security Mechanisms in TOE Evaluations, Observation Decisions Review Board
• PD 0112: Can a non-hardware TOE claim conformance with FPT_SEP.1?, Observation Decisions Review Board
• PD 0111: Clarify the Definitive Source of International Interps, Observation Decisions Review Board
• Re: Conditional SFRs within an ST, NIAP Interpretations Board
• Re: IDS System Components, NIAP Interpretations Board
• NIB Postings: Third Times The Charm!, NIAP Interpretations Board
• RE: FPT_SEP in an Application TOE (does mutual recognition work?), Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Stoneburner, Gary R.
    • Re: FPT_SEP in an Application TOE (does mutual recognition work?), Helmut Kurth
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Arnold, James L. Jr.
    • Re: FPT_SEP in an Application TOE (does mutual recognition work?), Helmut Kurth
    • Re: FPT_SEP in an Application TOE (does mutual recognition work?), Dirk-Jan Out
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Arnold, James L. Jr.
    • Re: FPT_SEP in an Application TOE (does mutual recognition work?), Helmut Kurth
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Arnold, James L. Jr.
    • Re: FPT_SEP in an Application TOE (does mutual recognition work?), Dirk-Jan Out
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE (does mutual recognition work?), Stoneburner, Gary R.
• RE: Assets definition, Stoneburner, Gary R.
• RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • Re: FPT_SEP in an Application TOE, Jim Fink
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Hal W Forsberg
  • RE: FPT_SEP in an Application TOE, Jim Fink
    • RE: FPT_SEP in an Application TOE, Nir Naaman
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Hal W Forsberg
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Hal W Forsberg
  • RE: FPT_SEP in an Application TOE, Stoneburner, Gary R.
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
    • RE: FPT_SEP in an Application TOE, Nir Naaman
  • RE: FPT_SEP in an Application TOE, Hal W Forsberg
  • Re: FPT_SEP in an Application TOE, Stoneburner, Gary R.
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Stoneburner, Gary R.
    • RE: FPT_SEP in an Application TOE, Nir Naaman
  • RE: FPT_SEP in an Application TOE, Stoneburner, Gary R.
    • Re: FPT_SEP in an Application TOE, YOKOTA HIROFUMI
  • Re: FPT_SEP in an Application TOE, Greg Bremen
    • Re: FPT_SEP in an Application TOE, YOKOTA HIROFUMI
      • RE: FPT_SEP in an Application TOE, Nir Naaman
      • Re: FPT_SEP in an Application TOE, YOKOTA HIROFUMI
      • Re: FPT_SEP in an Application TOE, Dirk-Jan Out
      • Re: FPT_SEP in an Application TOE, YOKOTA HIROFUMI
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
    • Assets definition, YOKOTA HIROFUMI
      • Re: Assets definition, Dirk-Jan Out
      • RE: Assets definition, Nir Naaman
    • Re: FPT_SEP in an Application TOE, Dirk-Jan Out
  • RE: FPT_SEP in an Application TOE, Arnold, James L. Jr.
  • RE: FPT_SEP in an Application TOE, Stoneburner, Gary R.
    • RE: FPT_SEP in an Application TOE, Nir Naaman
  • Re: FPT_SEP in an Application TOE, NIAP Interpretations Board
    • Re: FPT_SEP in an Application TOE, YOKOTA HIROFUMI
• Conditional SFRs within an ST ..., Trey Henefield
• IDS System Components ..., Trey Henefield
• Application TOE SFRs, Arnold, James L. Jr.
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Michelle A. Ruppel
    • RE: Application TOE SFRs, Daniel P. Faigin
    • Re: Application TOE SFRs, YOKOTA HIROFUMI
  • RE: Application TOE SFRs, Compton, Tammy S.
  • RE: Application TOE SFRs, Hal W Forsberg
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Hal W Forsberg
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Hal W Forsberg
  • RE: Application TOE SFRs, Stoneburner, Gary R.
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Michelle A. Ruppel
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Hal W Forsberg
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Arnold, James L. Jr.
    • RE: Application TOE SFRs, Daniel P. Faigin
  • RE: Application TOE SFRs, Hal W Forsberg
  • RE: Application TOE SFRs, Hal W Forsberg
    • FPT_SEP in an Application TOE, Franklin Haskell
      • Re: FPT_SEP in an Application TOE, YOKOTA HIROFUMI
  • Re: Application TOE SFRs, NIAP Interpretations Board
• demise of AMA?, Knoke, Jim
  • Re: Demise of AMA?, NIAP Interpretations Board
• Re: FDP_ITC.1.2 and the phrase 'security attibutes associated with the user data', YOKOTA HIROFUMI
• I-0480: Components Written As Environmental Actions, NIAP Interpretations Board
  • Re: I-0480: Components Written As Environmental Actions, YOKOTA HIROFUMI
  • Re: I-0480: Components Written As Environmental Actions, YOKOTA HIROFUMI
  • Re: I-0480: Components Written As Environmental Actions, YOKOTA HIROFUMI
    • Re: I-0480: Components Written As Environmental Actions, YOKOTA HIROFUMI
  • RE: I-0480: Components Written As Environmental Actions, Nir Naaman
  • RE: I-0480: Components Written As Environmental Actions, Stoneburner, Gary R.
  • Re: I-0480: Components Written As Environmental Actions, Hal W Forsberg
  • Re: I-0480: Components Written As Environmental Actions, NIAP Interpretations Board
    • Re: I-0480: Components Written As Environmental Actions, YOKOTA HIROFUMI
  • Re: I-0480: Components Written As Environmental Actions, NIAP Interpretations Board
• I-0479: FTP_ITC.1.3 Specifies The Functions Needing A Trusted Channel, NIAP Interpretations Board
  • Re: I-0479: FTP_ITC.1.3 Specifies The Functions Needing A Trusted Channel, NIAP Interpretations Board
• Re: FMT_MSA.3: Restrictive/ Permissive Default Values, NIAP Interpretations Board
  • RE: FMT_MSA.3: Restrictive/ Permissive Default Values, Arnold, James L. Jr.
    • RE: FMT_MSA.3: Restrictive/ Permissive Default Values, Nir Naaman
    • RE: FMT_MSA.3: Restrictive/ Permissive Default Values, Daniel P. Faigin
• Re: Draft interpretation RI#220 (FCS CKM/COP depending on FDP_ITC.1), NIAP Interpretations Board
  • Re: Draft interpretation RI#220 (FCS CKM/COP depending on FDP_ITC.1), YOKOTA HIROFUMI
• Withdrawal of CC Certificates, NIAP Interpretations Board
• PD 0109: Multiple Hardware Models with Different SFRs in One Security Target, Observation Decisions Review Board
  • FDP_ITC.1.2 and the phrase 'security attibutes associated with the user data', YOKOTA HIROFUMI
• PD 0110: Actions/Information Required of the Developer and Evaluator When Performing ADV_RCR Work, Observation Decisions Review Board
• Fwd: Re: no bolding in CC v2.2 Part 3, Gary Stoneburner
• CEM ACM_CAP.[2-4]-1 Clarification, Michelle A. Ruppel
  • Re: CEM ACM_CAP.[2-4]-1 Clarification, Greg Bremen
  • Re: CEM ACM_CAP.[2-4]-1 Clarification, NIAP Interpretations Board
• Archive of CCIMB interpretations, Paul Bicknell
  • Archive of CCIMB interpretations, Daniel P. Faigin
  • RE: Archive of CCIMB interpretations, Arnold, James L. Jr.
  • RE: Archive of CCIMB interpretations, Bottomly, Ronald J.
  • Re: Archive of CCIMB interpretations, NIAP Interpretations Board
• Interpretations Web Page, Michelle A. Ruppel
  • Re: Interpretations Web Page, NIAP Interpretations Board
• PD 0108: FTP_ITC.1.3 Specifies The Functions For Which A Trusted Channel Is Provided, Observation Decisions Review Board
  • Re: PD 0108: FTP_ITC.1.3 Specifies The Functions For Which A Trusted Channel Is Provided, Tom Benkart
    • Re: PD 0108: FTP_ITC.1.3 Specifies The Functions For Which A Trusted Channel Is Provided, Daniel P. Faigin
  • Re: PD 0108: FTP_ITC.1.3 Specifies The Functions For Which A Trusted Channel Is Provided, Observation Decisions Review Board
• PD 0107: IDSSPP v1.4: FPT_STM.1 Must Be Met by the TOE, Observation Decisions Review Board
  • RE: PD 0107: IDSSPP v1.4: FPT_STM.1 Must Be Met by the TOE, Arnold, James L. Jr.
    • Message not available
      • RE: PD 0107: IDSSPP v1.4: FPT_STM.1 Must Be Met by the TOE, Gary Stoneburner
    • RE: PD 0107: IDSSPP v1.4: FPT_STM.1 Must Be Met by the TOE, Daniel P. Faigin
• Clarification of rules when incorporating NIAP interps, Tom Benkart
  • Clarification of rules when incorporating NIAP interps, Daniel P. Faigin
    • Re: Clarification of rules when incorporating NIAP interps, Tom Benkart
      • Re: Clarification of rules when incorporating NIAP interps, Daniel P. Faigin
      • Re: Clarification of rules when incorporating NIAP interps, Tom Benkart
  • RE: Clarification of rules when incorporating NIAP interps, Creech, Justin
  • RE: Clarification of rules when incorporating NIAP interps, Arnold, James L. Jr.
  • Re: Clarification of rules when incorporating NIAP interps, NIAP Interpretations Board
  • RE: Clarification of rules when incorporating NIAP interps, Arnold, James L. Jr.
    • RE: Clarification of rules when incorporating NIAP interps, Daniel P. Faigin
      • RE: Clarification of rules when incorporating NIAP interps, Tom Benkart
      • Re: Clarification of rules when incorporating NIAP interps, Paul Bicknell
      • RE: Clarification of rules when incorporating NIAP interps, Daniel P. Faigin
  • Re: Clarification of rules when incorporating NIAP interps, NIAP Interpretations Board
  • RE: Clarification of rules when incorporating NIAP interps, Arnold, James L. Jr.
    • Message not available
      • RE: Clarification of rules when incorporating NIAP interps, Tom Benkart
  • RE: Clarification of rules when incorporating NIAP interps, Carpenter, Diann
  • RE: Clarification of rules when incorporating NIAP interps, Stoneburner, Gary R.
  • Re: Clarification of rules when incorporating NIAP interps, NIAP Interpretations Board
• RE: The term "argued away", Apted, Tony J. [RA]
  • Re: The term "argued away", NIAP Interpretations Board
• Re: How to express the TSP in SFRs for a simple encryption box, YOKOTA HIROFUMI
  • Re: How to express the TSP in SFRs for a simple encryption box, Gary Stoneburner
    • Re: How to express the TSP in SFRs for a simple encryption box, YOKOTA HIROFUMI
  • Re: How to express the TSP in SFRs for a simple encryption box, NIAP Interpretations Board
• FMT_MSA.3: Restrictive/Permissive Default Values, Arnold, James L. Jr.
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Nir Naaman
    • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Nir Naaman
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Nir Naaman
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
    • How to express the TSP in SFRs for a simple encryption box, YOKOTA HIROFUMI
  • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
    • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Arnold, James L. Jr.
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Arnold, James L. Jr.
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Arnold, James L. Jr.
    • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Arnold, James L. Jr.
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Arnold, James L. Jr.
    • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
    • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Nir Naaman
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
      • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Nir Naaman
      • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Tom Benkart
      • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Nir Naaman
      • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Dawn Adams
      • Meaning of TSP (WAS: FMT_MSA.3: Restrictive/Permissive Default Values), Nir Naaman
      • Re: Meaning of TSP (WAS: FMT_MSA.3: Restrictive/Permissive Default Values), Dawn Adams
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
      • Withdrawal of CC Certificates, Nir Naaman
    • Re: FMT_MSA.3: Restrictive/Permissive Default Values, YOKOTA HIROFUMI
      • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Bottomly, Ronald J.
    • The term "argued away", YOKOTA HIROFUMI
  • RE: FMT_MSA.3: Restrictive/Permissive Default Values, Apted, Tony J. [RA]
    • Re: FMT_MSA.3: Restrictive/Permissive Default Values, Dr.Ir. D.J. Out
• Re: Draft Interpretation for RI 178 - FAU confuses "audited" and "auditable", NIAP Interpretations Board
  • Re: Draft Interpretation for RI 178 - FAU confuses "audited" and "auditable", Dr.Ir. D.J. Out
    • Re: Draft Interpretation for RI 178 - FAU confuses "audited" and "auditable", Daniel P. Faigin
• I-0468: Must Test Setup And Cleanup Code Run Unprivileged?, NIAP Interpretations Board
• Re: Information Flow, NIAP Interpretations Board
  • Re: Information Flow, Magosányi Árpád
    • Re: Information Flow, Daniel P. Faigin
• I-0469: What Does "Initial Startup" Mean For FPT_AMT And FPT_TST?, NIAP Interpretations Board
  • I-0469: What Does "Initial Startup" Mean For FPT_AMT And FPT_TST?, NIAP Interpretations Board
  • Re: I-0469: What Does "Initial Startup" Mean For FPT_AMT And FPT_TST?, NIAP Interpretations Board
• Re: PD-0097: Compliance with IDS System PP Export Requirements, Observation Decisions Review Board
  • RE: PD-0097: Compliance with IDS System PP Export Requirements, Arnold, James L. Jr.
    • RE: PD-0097: Compliance with IDS System PP Export Requirements, Daniel P. Faigin
• Re: Questions about if Common Criteria is used in certain areas, NIAP Interpretations Board
• PD-0105: Acceptability of IKE Authentication as "Single Use" In Firewall PPs, Observation Decisions Review Board
• PD-0106: Situations Where AGD_USR May Be Vacuously Satisfied, Observation Decisions Review Board
• PD-0104: Testing All Claimed Platforms, Observation Decisions Review Board
• I-0477: Management Of Subject Attributes, NIAP Interpretations Board
• FDP Policies and Subject-to-subject Transfers, NIAP Interpretations Board
• Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, montse
  • RE: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, Nir Naaman
  • RE: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, montse
  • Re: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, NIAP Interpretations Board
  • RE: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, Arnold, James L. Jr.
  • Re: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, NIAP Interpretations Board
    • Re: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, YOKOTA HIROFUMI
  • Re: Interpretation of FAU_SEL.1.1 and FAU_STG.4.1, NIAP Interpretations Board
    • FIA_UID interpretations, Michelle A. Ruppel
      • TOE unique identifiers for hardware, Michelle Ruppel
• cc-cmt question about IT Environment SFRs in PPs and STs, Tom Benkart
  • Re: cc-cmt question about IT Environment SFRs in PPs and STs, Dr.Ir. D.J. Out
    • Draft interpretation RI#220 (FCS CKM/COP depending on FDP_ITC.1), YOKOTA HIROFUMI
      • Re: Draft interpretation RI#220 (FCS CKM/COP depending on FDP_ITC.1), Dr.Ir. D.J. Out
• RE: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Pamela.Grannum
  • RE: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Daniel P. Faigin
    • Re: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Dr.Ir. D.J. Out
      • Re: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Daniel P. Faigin
    • Re: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), YOKOTA HIROFUMI
      • Re: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Dr.Ir. D.J. Out
      • Re: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), YOKOTA HIROFUMI
      • Re: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Dr.Ir. D.J. Out
  • RE: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Arnold, James L. Jr.
  • RE: Categorisation of SFRs for the TOE and for the IT environment (flawed PPs), Arnold, James L. Jr.
• Categorisation of SFRs for the TOE and for the IT environment, Agievich Sergei V.
  • Re: Categorisation of SFRs for the TOE and for the IT environment, YOKOTA HIROFUMI
    • Re: Categorisation of SFRs for the TOE and for the IT environment, Dr.Ir. D.J. Out
      • Re: Categorisation of SFRs for the TOE and for the IT environment, Daniel P. Faigin
      • Re: Categorisation of SFRs for the TOE and for the IT environment, Dr.Ir. D.J. Out
  • RE: Categorisation of SFRs for the TOE and for the IT environment, RJBotto
    • RE: Categorisation of SFRs for the TOE and for the IT environment, Daniel P. Faigin
  • RE: Categorisation of SFRs for the TOE and for the IT environment, Arnold, James L. Jr.
  • RE: Categorisation of SFRs for the TOE and for the IT environment, Apted, Tony J. [RA]
  • RE: Categorisation of SFRs for the TOE and for the IT environment, Arnold, James L. Jr.
    • RE: Categorisation of SFRs for the TOE and for the IT environment, Daniel P. Faigin
      • Re: Categorisation of SFRs for the TOE and for the IT environment, Dr.Ir. D.J. Out
  • Categorisation of SFRs for the TOE and for the IT environment, NIAP Interpretations Board
• New ETR Format (LabGram#027), YOKOTA HIROFUMI
  • Re: New ETR Format (LabGram#027), Paul Bicknell
    • Re: New ETR Format (LabGram#027), Dr.Ir. D.J. Out
    • Re: New ETR Format (LabGram#027), Olin Sibert
  • New ETR Format (LabGram#027), Daniel P. Faigin
    • Re: New ETR Format (LabGram#027), YOKOTA HIROFUMI
  • RE: New ETR Format (LabGram#027), Arnold, James L. Jr.
    • Re: New ETR Format (LabGram#027), YOKOTA HIROFUMI
  • Re: New ETR Format (LabGram#027), NIAP Interpretations Board
• commoncriteriaportal.org, Dr.Ir. D.J. Out
  • commoncriteriaportal.org, Daniel P. Faigin
  • RE: commoncriteriaportal.org, Arnold, James L. Jr.
  • RE: commoncriteriaportal.org, RJBotto
• The International CC Web Page, Krall Ed-P27726
  • Re: The International CC Web Page, Magosányi Árpád
  • Re: The International CC Web Page, Dr.Ir. D.J. Out
    • Questions about if Common Criteria is used in certain areas, Enrique Vargas
• Evaluation of deployed IT systems? composition and risk management, Magosányi Árpád
  • Re: Evaluation of deployed IT systems? Composition and Risk Management, NIAP Interpretations Board
• Re: Statement of FMT_MSA.3.2, NIAP Interpretations Board
• Re: Do we need explicitly stated IT security requirement for FPT_STM?, NIAP Interpretations Board
• Re: RI # 178 - FAU confuses "audited" and "auditable", NIAP Interpretations Board
• PD-0102: CIMC PP Compliance for Iterated Requirements that are Satisfied by the IT Environment, Observation Decisions Review Board
• PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Observation Decisions Review Board
  • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
    • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
    • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Dr.Ir. D.J. Out
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • RE: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Nir Naaman
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Daniel P. Faigin
      • RE: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Nir Naaman
      • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Magosányi Árpád
  • Re: PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Observation Decisions Review Board
  • PD-0101: Level of Detail Necessary for Assurance Requirements on Third Party Products, Observation Decisions Review Board
• PD-0100: When can evaluation evidence be reused?, Observation Decisions Review Board
• PD-0103: Clarify CCEVS Policy for Applying NIAP Interpretations, Observation Decisions Review Board
• Re: RI # 177 - Meaning of "least upper bound" and "greatest lower bound", NIAP Interpretations Board
• Re: RI # 180 - COV.3 dependency on FSP.1, NIAP Interpretations Board
• Re: RI # 220 - FCS_CKM/COP dependency on FDP_ITC.1, NIAP Interpretations Board
• Re: RI # 192 - Sequencing of sub-activities, NIAP Interpretations Board
• Email account utilization warning., noreply
• Minor RI Issues (#3, #4, & #38), Arnold, James L. Jr.
  • Minor RI Issues (#3, #4, & #38), Daniel P. Faigin
  • RE: Minor RI Issues (#3, #4, & #38), Simpson, Randy
    • Re: Minor RI Issues (#3, #4, & #38), Dr.Ir. D.J. Out
• [Fwd: Announcement of Common Criteria Discussion List], David Ochel
  • [Fwd: Announcement of Common Criteria Discussion List], Daniel P. Faigin
  • RE: [Fwd: Announcement of Common Criteria Discussion List], Foreman, Elizabeth A.
• Replacement site for commoncriteria.org, Dr.Ir. D.J. Out
  • Re: Replacement site for commoncriteria.org, Gary Stoneburner
    • Re: Replacement site for commoncriteria.org, Dr.Ir. D.J. Out
  • RE: Replacement site for commoncriteria.org, AWLewis
    • Re: Replacement site for commoncriteria.org, Magosányi Árpád
    • RE: Replacement site for commoncriteria.org, Daniel P. Faigin
  • RE: Replacement site for commoncriteria.org, Krall Ed-P27726
    • Re: Replacement site for commoncriteria.org, YOKOTA HIROFUMI
• FCS_COP and FCS_CKM interdependency, Magosányi Árpád
  • RE: FCS_COP and FCS_CKM interdependency, Nir Naaman
  • RE: FCS_COP and FCS_CKM interdependency, Arnold, James L. Jr.
    • Re: FCS_COP and FCS_CKM interdependency, YOKOTA HIROFUMI
    • RE: FCS_COP and FCS_CKM interdependency, Michelle A. Ruppel
      • Re: FCS_COP and FCS_CKM interdependency, Dr.Ir. D.J. Out
  • RE: FCS_COP and FCS_CKM interdependency, Janardhana Pulugurtha
  • Re: FCS_COP and FCS_CKM interdependency, NIAP Interpretations Board
• RI#103 and #104, Arnold, James L. Jr.
• RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Arnold, James L. Jr.
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Daniel P. Faigin
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Arnold, James L. Jr.
    • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Daniel P. Faigin
    • Re: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Dr.Ir. D.J. Out
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Carpenter, Diann
    • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Daniel P. Faigin
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Apted, Tony J. [RA]
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Pamela.Grannum
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Arnold, James L. Jr.
    • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, Daniel P. Faigin
      • RE: Final Interpretation for RI 137 - Rules governing binding should be specifiable, Gary Stoneburner
  • RE: Final Interpretation for RI 137 - Rules governing binding sho uld be specifiable, RJBotto
• Draft Interpretation for RI 178 - FAU confuses "audited" and "au ditable", RJBotto
  • RE: Draft Interpretation for RI 178 - FAU confuses "audited" and "au ditable", Arnold, James L. Jr.
• Draft Interpretation for RI 177 - Meaning of "least upper bound" and "greatest lower bound", RJBotto
• Closed Statement for RI 234 - The minimum number of each type of security attribute, RJBotto
• Closed Statement for RI 248 - List Of Subjects And Objects Refers To Types Thereof, RJBotto
• Final Interpretation for RI 137 - Rules governing binding should be specifiable, RJBotto
  • RE: Final Interpretation for RI 137 - Rules governing binding should be specifiable, Gary Stoneburner
    • Re: Final Interpretation for RI 137 - Rules governing binding should be specifiable, YOKOTA HIROFUMI
      • Re: Final Interpretation for RI 137 - Rules governing binding should be specifiable, Gary Stoneburner
• Draft Interpretation for RI 192 - Sequencing of sub-activities, RJBotto
• Draft Interpretation for RI 220 - FCS_CKM/COP dependency on FDP_I TC.1, RJBotto
• Closed Statement for RI 102 - User Attributes to be Bound Should be Specified, RJBotto
• Interim Statement for RI 020 - SOF for cryptographic algorithms, RJBotto
• Draft Interpretation for RI 175 - Circular Arguments in the objec tives of FUN.2, RJBotto
• Closed Statement for RI 142 - Integrated Circuit Assurance, RJBotto
• Closed Statement for RI 206 - Point of Clarification, RJBotto
• Draft Interpretation for RI 180 - COV.3 dependency on FSP.1, RJBotto
• Closed Statement for RI 154 - CC is more than evaluation, RJBotto
• Draft Interpretation for RI 086 - Role of Sponsor, RJBotto
• RE: Clarification of term in Assurance Continuity requirements do cument, Apted, Tony J. [RA]
• FIPS Certification for Cryptographic Support, Ken Doris
  • Re: FIPS Certification for Cryptographic Support, Gary Stoneburner
  • RE: FIPS Certification for Cryptographic Support, Nir Naaman
  • RE: FIPS Certification for Cryptographic Support, Simpson, Randy
  • RE: FIPS Certification for Cryptographic Support, Arnold, James L. Jr.
  • RE: FIPS Certification for Cryptographic Support, JSPeder
• Clarification of term in Assurance Continuity requirements document, malnick
  • Clarification of term in Assurance Continuity requirements document, malnick
    • Re: Clarification of term in Assurance Continuity requirements document, YOKOTA HIROFUMI
      • Re: Clarification of term in Assurance Continuity requirements document, YOKOTA HIROFUMI
  • Re: Clarification of Term in Assurance Continuity Requirements Document, NIAP Interpretations Board
• Test Tool Specification, Krall Ed-P27726
  • Re: Test Tool Specification, YOKOTA HIROFUMI
    • Re: Test Tool Specification, Dr.Ir. D.J. Out
  • RE: Test Tool Specification, Arnold, James L. Jr.
  • RE: Test Tool Specification, Krall Ed-P27726
  • RE: Test Tool Specification, Arnold, James L. Jr.
  • Re: Test Tool Specification, NIAP Interpretations Board
  • RE: Test Tool Specification, Arnold, James L. Jr.
    • Re: Test Tool Specification, John Nilles
  • Re: Test Tool Specification, NIAP Interpretations Board
    • Re: Test Tool Specification, Tom Benkart
      • Re: Test Tool Specification, Gary Stoneburner
      • Re: Test Tool Specification, Daniel P. Faigin
  • RE: Test Tool Specification, Arnold, James L. Jr.
  • RE: Test Tool Specification, Stephen Brackin
  • Re: Test Tool Specification, NIAP Interpretations Board
• RE: Handling of a final interpretation, Arnold, James L. Jr.
  • Re: Handling of a final interpretation, Dr.Ir. D.J. Out
    • Re: Handling of a final interpretation, YOKOTA HIROFUMI
  • Re: Handling of a Final Interpretation, NIAP Interpretations Board
• unique reference to the TOE, Magosányi Árpád
  • Re: Unique reference to the TOE, NIAP Interpretations Board
• RE: I-0442: Restrictive Is Not Fully Defined Without Specificatio n Of Attributes, Arnold, James L. Jr.
• FIA_UID/FIA_UAU Hierarchy, Arnold, James L. Jr.
  • FIA_UID/FIA_UAU Hierarchy, Daniel P. Faigin
  • RE: FIA_UID/FIA_UAU Hierarchy, Arnold, James L. Jr.
    • RE: FIA_UID/FIA_UAU Hierarchy, Nir Naaman
  • RE: FIA_UID/FIA_UAU Hierarchy, Arnold, James L. Jr.
  • RE: FIA_UID/FIA_UAU Hierarchy, Arnold, James L. Jr.
• PD-0099: FIA_UID.2, FIA_UAU.2, and FPT_STM.1 Requirements: On the IT Environment?, Arnold, James L. Jr.
  • RE: PD-0099: FIA_UID.2, FIA_UAU.2, and FPT_STM.1 Requirements: On the IT Environment?, RJBotto
  • Re: PD-0099: FIA_UID.2, FIA_UAU.2, and FPT_STM.1 Requirements: On the IT Environment?, NIAP Interpretations Board
• RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
  • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Daniel P. Faigin
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
    • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
      • RE: PD-0091: Dependencies of Requirements on the IT Environment, Nir Naaman
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
    • RE: PD-0091: Dependencies of Requirements on the IT Environment, Daniel P. Faigin
    • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
    • RE: PD-0091: Dependencies of Requirements on the IT Environment, Daniel P. Faigin
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
    • RE: PD-0091: Dependencies of Requirements on the IT Environment, Daniel P. Faigin
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
    • RE: PD-0091: Dependencies of Requirements on the IT Environment, Daniel P. Faigin
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
    • RE: PD-0091: Dependencies of Requirements on the IT Environment, Daniel P. Faigin
  • RE: PD-0091: Dependencies of Requirements on the IT Environment, Arnold, James L. Jr.
  • Re: PD-0091: Dependencies of Requirements on the IT Environment, NIAP Interpretations Board
• Fwd: Error Condition Re: RE: PD-0091: Dependencies of Requirements on the IT Environment, Gary Stoneburner
  • RE: Error Condition Re: RE: PD-0091: Dependencies of Requirements on the IT Environment, Nir Naaman
• location for list archives, Gary Stoneburner
• FW: tool for creating ST and PP?, Akhilesh Dhawan
  • FW: tool for creating ST and PP?, Daniel P. Faigin
• RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Apted, Tony J.
  • RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Daniel P. Faigin
    • tool for creating ST and PP?, Akhilesh Dhawan
    • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, YOKOTA HIROFUMI
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, YOKOTA HIROFUMI
      • RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Nir Naaman
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, YOKOTA HIROFUMI
      • RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Nir Naaman
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, YOKOTA HIROFUMI
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, Magosányi Árpád
      • PD-0091: Dependencies of Requirements on the IT Environment, YOKOTA HIROFUMI
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Gary Stoneburner
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Ken Elliott III
      • RE: PD-0091: Dependencies of Requirements on the IT Environment, Nir Naaman
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Ken Elliott III
      • RE: PD-0091: Dependencies of Requirements on the IT Environment, Nir Naaman
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Ken Elliott III
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, YOKOTA HIROFUMI
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Ken Elliott III
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Tom Benkart
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Ken Elliott III
      • Re: PD-0091: Dependencies of Requirements on the IT Environment, Dr.Ir. D.J. Out
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, YOKOTA HIROFUMI
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, Gary Stoneburner
      • RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Nir Naaman
      • RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Gary Stoneburner
      • Re: Do we need explicitly stated IT security requirement for FPT_ STM?, Dr.Ir. D.J. Out
  • RE: Do we need explicitly stated IT security requirement for FPT_ STM?, Simpson, Randy
• CC Home Page, YOKOTA HIROFUMI
  • RE: CC Home Page, Pamela.Grannum
• clarification needed: ALC_FLR.3.6C, Magosányi Árpád
  • Re: Clarification needed: ALC_FLR.3.6C, NIAP Interpretations Board
• Archive Question, Eric J. Grimes
  • Archive Question, Daniel P. Faigin
    • Re: Archive Question, Magosányi Árpád
  • Re: Archive Question, NIAP Interpretations Board
• New kid in the block, Magosányi Árpád
• Re: I-0440: Clarification Of Detection/Prevention For FIA_UAU.3, NIAP Interpretations Board
  • Re: I-0440: Clarification Of Detection/Prevention For FIA_UAU.3, NIAP Interpretations Board
• Re: I-0451: When To Use IFF/IFC And ACF/ACC, NIAP Interpretations Board
  • Re: I-0451: When To Use IFF/IFC And ACF/ACC, NIAP Interpretations Board
    • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Nir Naaman
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Daniel P. Faigin
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, YOKOTA HIROFUMI
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Daniel P. Faigin
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Daniel P. Faigin
      • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Nir Naaman
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Gary Stoneburner
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Gary Stoneburner
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, YOKOTA HIROFUMI
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Magosányi Árpád
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • information flow, Magosányi Árpád
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Gary Stoneburner
      • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Nir Naaman
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Gary Stoneburner
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Magosányi Árpád
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Magosányi Árpád
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Gary Stoneburner
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Daniel P. Faigin
      • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Magosányi Árpád
    • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Michelle A. Ruppel
  • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Hal W Forsberg
    • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Dr.Ir. D.J. Out
  • Re: I-0451: When To Use IFF/IFC And ACF/ACC, Hal W Forsberg
  • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Arnold, James L. Jr.
    • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Daniel P. Faigin
  • RE: I-0451: When To Use IFF/IFC And ACF/ACC, Arnold, James L. Jr.
  • Re: I-0451: When To Use IFF/IFC And ACF/ACC, NIAP Interpretations Board
• Introduction to November 2003 Postings, NIAP Interpretations Board
• Re: MR on Assurances not in EAL1-4, NIAP Interpretations Board
• Understanding International Interpretation #0049, adamobrien
  • RE: Understanding International Interpretation #0049, Nir Naaman
    • Re: Understanding International Interpretation #0049, YOKOTA HIROFUMI
      • RE: Understanding International Interpretation #0049, Nir Naaman
      • Re: Understanding International Interpretation #0049, YOKOTA HIROFUMI
      • RE: Understanding International Interpretation #0049, Nir Naaman
      • RE: Understanding International Interpretation #0049, Gary Stoneburner
      • RE: Understanding International Interpretation #0049, Nir Naaman
      • Re: Understanding International Interpretation #0049, YOKOTA HIROFUMI
      • Do we need explicitly stated IT security requirement for FPT_STM?, YOKOTA HIROFUMI
      • Re: Do we need explicitly stated IT security requirement for FPT_STM?, YOKOTA HIROFUMI
      • RE: Do we need explicitly stated IT security requirement for FPT_STM?, Nir Naaman
      • Do we need explicitly stated IT security requirement for FPT_STM?, Daniel P. Faigin
  • Re: Understanding International Interpretation #0049, Hal W Forsberg
  • Re: Understanding International Interpretation #0049, NIAP Interpretations Board
• TFM and SFUG, Creech, Justin
  • Re: TFM and SFUG, NIAP Interpretations Board
  • RE: TFM and SFUG, Nash, Barry S.
  • RE: TFM and SFUG, Foreman, Elizabeth A.
  • RE: TFM and SFUG, Creech, Justin
  • RE: TFM and SFUG, Foreman, Elizabeth A.
• Interrelationship between PPs and Interps, Tom Benkart
  • RE: Interrelationship between PPs and Interps, Michelle A. Ruppel
    • Re: Interrelationship between PPs and Interps, YOKOTA HIROFUMI
  • Re: Interrelationship between PPs and Interps, NIAP Interpretations Board
• Does initial setting of rules-table need FMT_MSA.3?, YOKOTA HIROFUMI
  • RE: Does initial setting of rules-table need FMT_MSA.3?, Nir Naaman
    • Re: Does initial setting of rules-table need FMT_MSA.3?, YOKOTA HIROFUMI
      • RE: Does initial setting of rules-table need FMT_MSA.3?, Nir Naaman
  • RE: Does initial setting of rules-table need FMT_MSA.3?, Michelle A. Ruppel
    • RE: Does initial setting of rules-table need FMT_MSA.3?, Nir Naaman
  • Re: Does initial setting of rules-table need FMT_MSA.3?, YOKOTA HIROFUMI
    • can we certify an organisation with CC?, Akhilesh Dhawan
      • can we certify an organisation with CC?, Daniel P. Faigin
  • Re: Does initial setting of rules-table need FMT_MSA.3?, NIAP Interpretations Board
• Multiple PP conformance conflicts, James Arnold
  • Re: Multiple PP conformance conflicts, NIAP Interpretations Board
• Re: I-0451: When To Use IFF/IFC ( What is fundamental characteristic of information), YOKOTA HIROFUMI
  • Re: I-0451: When To Use IFF/IFC ( What is fundamental characteristic of information), Gary Stoneburner
    • Re: I-0451: When To Use IFF/IFC ( What is fundamental characteristic of information), YOKOTA HIROFUMI
      • Re: I-0451: When To Use IFF/IFC ( What is fundamental characteristic of information), Gary Stoneburner
      • Statement of FMT_MSA.3.2, YOKOTA HIROFUMI
• Question regarding refinements of SFRs impacted by NIAP interpretations, Tom Benkart
  • Re: Question regarding refinements of SFRs impacted by NIAP interpretations, Gary Stoneburner
    • Re: Question regarding refinements of SFRs impacted by NIAP interpretations, Tom Benkart
      • Re: Question regarding refinements of SFRs impacted by NIAP interpretations, Gary Stoneburner
  • Re: Question regarding refinements of SFRs impacted by NIAP interpretations, NIAP Interpretations Board
• TSF and design decomposition, YOKOTA HIROFUMI
  • RE: TSF and design decomposition, Nir Naaman
    • Re: TSF and design decomposition, YOKOTA HIROFUMI
      • Re: TSF and design decomposition, Daniel P. Faigin
      • Re: TSF and design decomposition, Gary Stoneburner
      • RE: TSF and design decomposition, Nir Naaman
  • TSF and design decomposition, Daniel P. Faigin
  • RE: TSF and design decomposition, Andrew Teklemariam
    • RE: TSF and design decomposition, Daniel P. Faigin
  • Re: TSF and design decomposition, NIAP Interpretations Board
• Re: Protection Profile Compliance - MRA, NIAP Interpretations Board
• MITM attack on CC/NIAP, Walt_Tuvell
  • Re: MITM attack on CC/NIAP, NIAP Interpretations Board
• I-0472: Correction Of Definition Of Lattice, NIAP Interpretations Board
  • Re: I-0472: Correction Of Definition Of Lattice, NIAP Interpretations Board
• Re: I-0433: Design Abstractions For Non-IT Mechanisms, NIAP Interpretations Board
  • Re: I-0433: Design Abstractions For Non-IT Mechanisms, NIAP Interpretations Board
  • Re: I-0433: Design Abstractions For Non-IT Mechanisms, NIAP Interpretations Board
• Re: I-0470: FPT_AMT When There Are No Operational (IT) Environment Objectives, NIAP Interpretations Board
• I-0473: Ability To Obtain The Unique Identifier Of The TOE, NIAP Interpretations Board
  • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, NIAP Interpretations Board
  • RE: I-0473: Ability To Obtain The Unique Identifier Of The TOE, Arnold, James L. Jr.
  • RE: I-0473: Ability To Obtain The Unique Identifier Of The TOE, Arnold, James L. Jr.
    • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, Dr.Ir. D.J. Out
  • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, NIAP Interpretations Board
    • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, Dr.Ir. D.J. Out
  • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, NIAP Interpretations Board
  • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, NIAP Interpretations Board
  • RE: I-0473: Ability To Obtain The Unique Identifier Of The TOE, Arnold, James L. Jr.
    • Re: I-0473: Ability To Obtain The Unique Identifier Of The TOE, Dr.Ir. D.J. Out
• I-0442: Restrictive Is Not Fully Defined Without Specification Of Attributes, NIAP Interpretations Board
  • Protection Profile Compliance - MRA, Sai Pulugurtha
  • Re: I-0442: Restrictive Is Not Fully Defined Without Specification Of Attributes, NIAP Interpretations Board
  • Re: I-0442: Restrictive Is Not Fully Defined Without Specification Of Attributes, NIAP Interpretations Board
• Re: I-0451: When To Use IFF/IFC And AFF/AFC, NIAP Interpretations Board
  • RE: I-0451: When To Use IFF/IFC And AFF/AFC, Michelle A. Ruppel
    • RE: I-0451: When To Use IFF/IFC And AFF/AFC, Nir Naaman
  • RE: I-0451: When To Use IFF/IFC And AFF/AFC, Carpenter, Diann
    • RE: I-0451: When To Use IFF/IFC And AFF/AFC, Nir Naaman
  • Re: I-0451: When To Use IFF/IFC And AFF/AFC, NIAP Interpretations Board
• Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Ken Elliott III
    • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Tom Benkart
      • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Gary Stoneburner
  • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Burgio Joanne E. J9C687
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
    • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Nir Naaman
      • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Daniel P. Faigin
      • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Wendi Ittah
      • MR on Assurances not in EAL1-4, RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Gary Stoneburner
      • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Gary Stoneburner
      • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, YOKOTA HIROFUMI
    • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Ken Elliott III
      • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Daniel P. Faigin
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
    • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Nir Naaman
      • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Gary Stoneburner
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Hal W Forsberg
    • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Gary Stoneburner
    • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Daniel P. Faigin
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Hal W Forsberg
    • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Daniel P. Faigin
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
  • RE: I-0434: Treatment Of TSF Components Provided By A Third-Party, Arnold, James L. Jr.
    • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, Magosányi Árpád
  • I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
  • Re: I-0434: Treatment Of TSF Components Provided By A Third-Party, NIAP Interpretations Board
• Introductory Message for July Postings, NIAP Interpretations Board
• Re: I-417: Association Of Information Flow Attributes W/Subjects And Information, NIAP Interpretations Board
• Re: Error check of Input message using IFC, NIAP Interpretations Board
• List change - only subscribers can now post, Gary Stoneburner
• {Spam?} Promote your business, billy
• =?windows-1255?Q?=E4=EC=E5=E7_=E4=E0=E9=F0=E8=F8=F0=E8=E9_=EE=E4=E3=E5=F8=E4_=EE=F1'_13?=,
• {Spam?} =?GB2312?B?zfjC59OyxczCvM/gu/o=?= 6:44:43:911, =?GB2312?B?MDczMS04ODA4NTYyz+O56bXn19PT0M/euavLvg==?=
• =?windows-1255?Q?=E4=EC=E5=E7_=E4=E0=E9=F0=E8=F8=F0=E8=E9_=EE=E4=E3=E5=F8=E4_=EE=F1'_12_?=,
• {Spam?} =?GB2312?B?zf7B+tOqz/rGvcyoo6zIq8Pms8/V97T6wO0=?= 7:26:1:421, =?GB2312?B?zf7B+tOqz/rGvcyoo6zIq8Pms8/V97T6wO0=?=
• {Spam?} =?GB2312?B?tNnP+tDCxrctueO45rfJx/KjqL2hye3Tw8a3o6k=?= 21:22:5, =?GB2312?B?ye7b2srQs6yxpsP50anA8ca3s6c=?=
• TSF Self Testing, Arnold, James L. Jr.
  • Re: TSF Self Testing, NIAP Interpretations Board
• {Spam?} =?GB2312?B?xvPStbXn19PJzM7x?= 15:30:3:935, =?GB2312?B?u7bTrbfDzso=?=
• RE: [I-0464: Conditional Requirements], Bradford O'Neill
• RE: [I-0461: Definition of TSF: Relied Upon For The Correction Enforcement], Bradford O'Neill
  • Re: [I-0461: Definition of TSF: Relied Upon For The Correction Enforcement], YOKOTA HIROFUMI
• Re: [Fwd: I-0470: FPT_AMT When There Are No Operational Environment Objectives], Jean Hung
• Re: [Fwd: I-0436: Compliance Claims Against A Flawed PP], Jean Hung
• Re: [Fwd: I-0467: Can Guidance Documentation Meet TSF Requirements?], Yi-Fang Koh
• RE: I-0470: FPT_AMT When There Are No Operational Environment Obj ectives, Arnold, James L. Jr.
• {Spam?} =?GB2312?B?zf7B+tOqz/rGvcyoo6zIq8Pms8/V97T6wO0=?= 17:33:33:4, =?GB2312?B?zf7B+tOqz/rGvcyoo6zIq8Pms8/V97T6wO0=?=
• {Spam?} =?GB2312?B?z/LE+s3GvPbSu7/uuN/Q1Lzbsci1xLfAu/DHvaOos8LWx8H6o6k=?=, =?GB2312?B?s8LWx8H6?=
• {Spam?} =?GB2312?B?xbfKvUNEutA=?= 18:26:32:560, =?GB2312?B?ye7b2srQs6yxpsP50anA8ca3s6c=?=
• RE: Where can we use Information flow control policy (FDP_IFC/IFF)?, Andrew Teklemariam
  • Re: Where can we use Information flow control policy (FDP_IFC/IFF)?, YOKOTA HIROFUMI
  • RE: Where can we use Information flow control policy (FDP_IFC/IFF)?, Andrew Teklemariam
    • Re: Where can we use Information flow control policy (FDP_IFC/IFF)?, YOKOTA HIROFUMI
  • Re: Where can we use Information flow control policy (FDP_IFC/IFF)?, NIAP Interpretations Board
• =?windows-1255?Q?=E4=EC=E5=E7_=E4=E0=E9=F0=E8=F8=F0=E8=E9_=EE=E4=E3=E5=F8=E4_9?=,
• RE: Relationship between the TOE and the product, Andrew Teklemariam
  • RE: Relationship between the TOE and the product, Nir Naaman
    • Where can we use Information flow control policy (FDP_IFC/IFF)?, YOKOTA HIROFUMI
  • Re: Relationship between the TOE and the product, NIAP Interpretations Board
• cast iron Christmas tree stand, fengyuana1989
• {Spam?} =?GB2312?B?s8m5pr6twO3Iy01UULncwO2yxcTct6LVuQ==?= 9:10:17:80, =?GB2312?B?vquy37ncwO0=?=
• {Spam?} =?GB2312?B?Q0S60A==?= 9:56:11:210, =?GB2312?B?ye7b2srQs6yxpsP50anA8ca3s6c=?=
• RE: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, Shari Galitzer
  • Re: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, YOKOTA HIROFUMI
  • Re: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, NIAP Interpretations Board
    • Re: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, YOKOTA HIROFUMI
      • Re: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, YOKOTA HIROFUMI
  • Re: Re: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, NIAP Interpretations Board
• {Spam?} =?GB2312?B?xvPStbXn19PJzM7x?= 16:45:43:118, =?GB2312?B?u7bTrbfDzso=?=
• {Spam?} =?GB2312?B?ye7b2srQ0cfMq9HQvr+74c3GvPbG89K1udzA7deo0rW94r72t72wuA==?=, hcc
• {Spam?} ÐÂÀ¶µçÆø ÖúÄúÒ»±ÛÖ®Á¦, Ïå·®ÊÐÐÂÀ¶µçÆøÓÐÏÞ¹«Ë¾
• =?GB2312?B?ytUsz/LE+s3GvPa159fTyczO8cD7xvc=?= 13:1:35:345, bobbie
• =?GB2312?B?VE+jumNjLWNtdEBuaXN0Lmdvdrvh1LHK1SE=?= 7:18:2:182, cbl
• ITV 22:17:40:433, =?GB2312?B?sbG+qczGt+fOxLuvvbvB99bQ0MQ=?=
• Is it acceptable to specify ACC/ACF when there is no explicit rules implemented, YOKOTA HIROFUMI
  • Re: Is it acceptable to specify ACC/ACF when there is no explicit rules implemented, NIAP Interpretations Board
• =?GB2312?B?tNnP+tDCxrfBvcjLzeY=?= 10:38:45:190, =?GB2312?B?ye7b2srQs6yxpsP50anA8ca3s6c=?=
• =?GB2312?B?zfXWvrarus3L+7XE0MLI7bz+IL66v6rQrc2s1q7Qxw==?= 8:55:, =?GB2312?B?ueO2q8qhye7b2srQz+O56bXn19PT0M/euavLvg==?=
• Re: The reasons of SFP(s) enforcement are not consistent, NIAP Interpretations Board
  • Re: The reasons of SFP(s) enforcement are not consistent, YOKOTA HIROFUMI
  • Error check of Input message using IFC, YOKOTA HIROFUMI
  • Is it acceptable to specify ACC/ACF when there is no explicit rules implemented, YOKOTA HIROFUMI
  • How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, YOKOTA HIROFUMI
    • RE: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, Nir Naaman
      • Re: How to express FMT_MTD.1 (Management of TSF data) requirement in the IT environment?, YOKOTA HIROFUMI
  • Re: The reasons of SFP(s) enforcement are not consistent, NIAP Interpretations Board
• Re: Level of description on Security requirements for the IT environment, NIAP Interpretations Board
• =?GB2312?B?0ryw29Sy1/bBvdbWSVSy+sa3tPrA7Q==?= 9:49:55:596, =?GB2312?B?0rDC7bmk1/fK0g==?=
• =?GB2312?B?yczWx8jtvP6/ycq5xPq1xNK1zvHM5c+11LbA67fHteTV/bOj1MvX9w==?=, soven
• =?GB2312?B?SVRW1fe2qbqv?= 19:9:49:647, =?GB2312?B?sbG+qczGt+fOxLuvvbvB99bQ0MQ=?=
• =?GB2312?B?s8m5pr6twO3Iy01UULncwO2yxcTct6LVuQ==?= 13:55:25:6, =?GB2312?B?vquy37ncwO0=?=
• Re: =?GB2312?B?0ryw29Sy1/bBvdbWSVSy+sa3tPrA7SAxMzo4OjEwOjUxNg==?=, Phil Loperfido
  • Re: =?GB2312?B?0ryw29Sy1/bBvdbWSVSy+sa3tPrA7SAxMzo4OjEwOjUxNg==?=, Daniel P. Faigin
• =?GB2312?B?0ryw29Sy1/bBvdbWSVSy+sa3tPrA7Q==?= 13:8:10:516, =?GB2312?B?0rDC7bmk1/fK0g==?=
• =?GB2312?B?xfPT0aOsxPrWqrXAwcvC8KO/?= 7:31:1:290, =?GB2312?B?zf7B+rXn19PJzM7xv8a8vNPQz965q8u+?=
• =?GB2312?B?xfPT0aOsxPrWqrXAwcvC8KO/?= 7:21:19:80, =?GB2312?B?zf7B+rXn19PJzM7xv8a8vNPQz965q8u+?=
• I-0470: FPT_AMT When There Are No Operational Environment Objectives, NIAP Interpretations Board
  • RE: I-0470: FPT_AMT When There Are No Operational Environment Objectives, Nir Naaman
    • Re: I-0470: FPT_AMT When There Are No Operational Environment Objectives, YOKOTA HIROFUMI
  • RE: I-0470: FPT_AMT When There Are No Operational Environment Objectives, Knoke, Jim
  • Re: I-0470: FPT_AMT When There Are No Operational Environment Objectives, NIAP Interpretations Board
• I-0436: Compliance Claims Against A Flawed PP, NIAP Interpretations Board
  • RE: I-0436: Compliance Claims Against A Flawed PP, Arnold, James L. Jr.
    • RE: I-0436: Compliance Claims Against A Flawed PP, Daniel P. Faigin
  • Re: I-0436: Compliance Claims Against A Flawed PP, NIAP Interpretations Board
  • Re: I-0436: Compliance Claims Against A Flawed PP, NIAP Interpretations Board
• I-0434: 3rd Party Hardware/Software And Assurance, NIAP Interpretations Board
  • Re: I-0434: 3rd Party Hardware/Software And Assurance, Timothy Bergendahl
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Knoke, Jim
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Daniel P. Faigin
      • RE: I-0434: 3rd Party Hardware/Software And Assurance, Alexander Henefield
      • Re: I-0434: 3rd Party Hardware/Software And Assurance, Dr.Ir. D.J. Out
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Shari Galitzer
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Knoke, Jim
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Nir Naaman
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Arnold, James L. Jr.
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Alexander Henefield
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Alexander Henefield
      • Re: I-0434: 3rd Party Hardware/Software And Assurance, Dr.Ir. D.J. Out
      • RE: I-0434: 3rd Party Hardware/Software And Assurance, Alexander Henefield
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Gilliatt, Jeff
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Trey Henefield
      • RE: I-0434: 3rd Party Hardware/Software And Assurance, Daniel P. Faigin
      • Relationship between the TOE and the product, YOKOTA HIROFUMI
      • Re: Relationship between the TOE and the product, YOKOTA HIROFUMI
      • RE: Relationship between the TOE and the product, Nir Naaman
      • Re: Relationship between the TOE and the product, YOKOTA HIROFUMI
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Shari Galitzer
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Daniel P. Faigin
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Nir Naaman
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Knoke, Jim
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Nir Naaman
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Simpson, Randy
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Michelle A. Ruppel
      • Re: I-0434: 3rd Party Hardware/Software And Assurance, James Donndelinger
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Arnold, James L. Jr.
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Daniel P. Faigin
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Simpson, Randy
    • Re: I-0434: 3rd Party Hardware/Software And Assurance, YOKOTA HIROFUMI
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Arnold, James L. Jr.
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Daniel P. Faigin
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Shari Galitzer
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Daniel P. Faigin
    • RE: I-0434: 3rd Party Hardware/Software And Assurance, Michelle A. Ruppel
      • RE: I-0434: 3rd Party Hardware/Software And Assurance, Alexander Henefield
  • RE: I-0434: 3rd Party Hardware/Software And Assurance, Shari Galitzer
  • Re: I-0434: 3rd Party Hardware/Software And Assurance, NIAP Interpretations Board
• I-0433: Design Abstractions For Mechanical Mechanisms, NIAP Interpretations Board
  • Re: I-0433: Design Abstractions For Mechanical Mechanisms, Timothy Bergendahl
  • RE: I-0433: Design Abstractions For Mechanical Mechanisms, Knoke, Jim
    • Re: I-0433: Design Abstractions For Mechanical Mechanisms, Dr.Ir. D.J. Out
      • Re: I-0433: Design Abstractions For Mechanical Mechanisms, Daniel P. Faigin
      • Re: I-0433: Design Abstractions For Mechanical Mechanisms, Dr.Ir. D.J. Out
  • Re: I-0433: Design Abstractions For Mechanical Mechanisms, NIAP Interpretations Board
• I-0467: Can Guidance Documentation Meet TSF Requirements?, NIAP Interpretations Board
  • Re: I-0467: Can Guidance Documentation Meet TSF Requirements?, NIAP Interpretations Board
• I-0464: Conditional Requirements, NIAP Interpretations Board
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
    • RE: I-0464: Conditional Requirements, Michelle A. Ruppel
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
  • RE: I-0464: Conditional Requirements, Arnold, James L. Jr.
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
  • Re: I-0464: Conditional Requirements, NIAP Interpretations Board
• Introductory Message for May Postings, NIAP Interpretations Board
  • RE: Introductory Message for May Postings, Arnold, James L. Jr.
    • RE: Introductory Message for May Postings, Daniel P. Faigin
  • RE: Introductory Message for May Postings, Arnold, James L. Jr.
  • RE: Introductory Message for May Postings, Arnold, James L. Jr.
    • RE: Introductory Message for May Postings, Daniel P. Faigin
  • Re: Introductory Message for May Postings, NIAP Interpretations Board
• =?GB2312?B?1PnK1NPD06rP+sa9zKg=?= 12:53:52:910, =?GB2312?B?zf7B+rXn19PJzM7xv8a8vNPQz965q8u+?=
• =?GB2312?B?ye7b2srQ0cfMq9HQvr+74dfJ0a/W0NDE08XQ472yyqbNxrz2?=, hcc
• =?GB2312?B?ufPX5cbl?= 9:59:43:720, =?GB2312?B?ye7b2srQs6yxpsP50anA8ca3s6c=?=
• =?GB2312?B?yf28ts2o1qqjoQ==?= 18:36:17:290, zh01
• =?GB2312?B?w+K30b+0yKvH8rXnytOjocnMvNLQ+7SrtcTK19Gho6E=?= 5:46, =?GB2312?B?sbG+qczGt+fOxLuvvbvB99bQ0MQ=?=
• =?GB2312?B?zf7B+tOqz/rGvcyoo6zIq8Pms8/V97T6wO0=?= 17:25:32:9, =?GB2312?B?zf7B+tOqz/rGvcyoo6zIq8Pms8/V97T6wO0=?=
• =?GB2312?B?0cfMq9HQvr+74c3GvPa8qNCnv7y6y7iotbzKtcqpt72wuA==?=, hcc
• BUSINESS PROPOSAL, rosemary01
• source codes, karl willies
• =?gb2312?q?www.0755sz.com(=D3=AA=CF=FA=CD=F8=C2=E7=A3=A9?=, =?gb2312?q?=D1=EE=CF=C8=C9=FA_?=
• =?GB2312?B?1ffH87f+17C31s/6x/61wKOotPrA7cnMo6k=?=, marketing
• =?GB2312?B?xvPStbXn19PJzM7x?= 7:23:32:731, =?GB2312?B?u7bTrbfDzso=?=
• ÍòµÂΪÄúÌṩ×îΪ·á¸»µÄÆóÒµÄÚѵ×ÊÔ´, shenzhen
• =?GB2312?B?VE+jus2o1qqjoQ==?= 13:45:17:470, web@vxyv.com
• =?GB2312?B?Rk9STTrJ/by2zajWqiHXqri61PDIy8rVLg==?= 7:47:11:613, =?GB2312?B?yczWx7Xn19PJzM7xyO28/g==?=
• =?GB2312?B?Uk86ye7b2su5yqK/xry8v6q3otPQz965q8u+zajWqg==?= 7:35:, panyue1999@sina.com
• =?GB2312?B?xPosz/LE+s3GvPbXrMeuwPvG9w==?= 21:20:57:836, =?GB2312?B?yczWx8jtvP4=?=
• No Subject, =?GB2312?B?s8LWx8H6?=
  • No Subject, Alan Gornall
• (±¤°í)National geographic ÀýÈ£ÀÇ Âù½º, ³×¼Å³ÎÁö¿À±×·¡ÇÈ
• To: cc-cmt as a Nicer Person, Dr. Carter, President
• Live Webinar: Surrender is Not an Option!, Bodacion Technologies
• How to write assumptions, YOKOTA HIROFUMI
  • Re: How to write assumptions, Dr.Ir. D.J. Out
    • Re: How to write assumptions, Gary Stoneburner
  • Fw: How to write assumptions, YOKOTA HIROFUMI
    • Re: Fw: How to write assumptions, Dr.Ir. D.J. Out
  • Re: How to write assumptions, YOKOTA HIROFUMI
    • Re: How to write assumptions, Dr.Ir. D.J. Out
      • Re: How to write assumptions, YOKOTA HIROFUMI
      • Re: How to write assumptions, Dr.Ir. D.J. Out
      • Re: How to write assumptions, Gary Stoneburner
      • Re: How to write assumptions, YOKOTA HIROFUMI
      • Re: How to write assumptions, Gary Stoneburner
      • Clarification Re: How to write assumptions, Gary Stoneburner
      • The reasons of SFP(s) enforcement are not consistent, YOKOTA HIROFUMI
      • Re: The reasons of SFP(s) enforcement are not consistent, Dr.Ir. D.J. Out
      • RE: The reasons of SFP(s) enforcement are not consistent, Nir Naaman
      • Re: The reasons of SFP(s) enforcement are not consistent, Dr.Ir. D.J. Out
      • RE: The reasons of SFP(s) enforcement are not consistent, Nir Naaman
      • RE: The reasons of SFP(s) enforcement are not consistent, Nir Naaman
      • Re: The reasons of SFP(s) enforcement are not consistent, YOKOTA HIROFUMI
      • Re: The reasons of SFP(s) enforcement are not consistent, Dr.Ir. D.J. Out
      • RE: The reasons of SFP(s) enforcement are not consistent, Nir Naaman
      • Re: The reasons of SFP(s) enforcement are not consistent, YOKOTA HIROFUMI
      • Re: The reasons of SFP(s) enforcement are not consistent, Dr.Ir. D.J. Out
      • Re: How to write assumptions, YOKOTA HIROFUMI
  • Re: How to write assumptions, NIAP Interpretations Board
    • Re: How to write assumptions, Dr.Ir. D.J. Out
  • Re: How to write assumptions, NIAP Interpretations Board
• =?euc-kr?B?KLGksO0pILy8sOggw9aw7SDH5riuv+y15SC757/uteXAxyDB+Lz2uKYgurg=?= =?euc-kr?B?v6m15biztM+02S4=?=, Soundwiz
• =?euc-kr?B?KLGksO0pIMLyx8+46SCz0b7uv8m0z7TZLiCzqrimIMHBvsbHz7DUIMfPtMIg?= =?euc-kr?B?w9a46S4uIMitwMzGrrWlwMwgwMy6pcau?=, HappySound
• (±¤°í) °í°´´Ô²² µå¸®´Â ¾Ï°ú ´ç´¢¿¡ ÁÁ´Ù´Â Â÷°¡¹ö¼¸, ÇÏÀÌÇｺ
• PP Problems: Requirement Redundancy, Arnold, James L. Jr.
  • Re: PP Problems: Requirement Redundancy, Gary Stoneburner
  • Re: PP Problems: Requirement Redundancy, NIAP Interpretations Board
  • RE: PP Problems: Requirement Redundancy, Arnold, James L. Jr.
    • RE: PP Problems: Requirement Redundancy, Daniel P. Faigin
• PP Problems: PP control of non-PP claims, Arnold, James L. Jr.
  • Re: PP Problems: PP control of non-PP claims, Gary Stoneburner
  • Re: PP Problems: PP control of non-PP claims, Hal W Forsberg
  • RE: PP Problems: PP control of non-PP claims, Arnold, James L. Jr.
  • Re: PP Problems: PP control of non-PP claims, NIAP Interpretations Board
• PP Problems: External Standards, Arnold, James L. Jr.
  • Re: PP Problems: External Standards, Gary Stoneburner
  • RE: PP Problems: External Standards, Arnold, James L. Jr.
    • RE: PP Problems: External Standards, Shawn Fitzgerald
  • RE: PP Problems: External Standards, Arnold, James L. Jr.
  • RE: PP Problems: External Standards, Shawn Fitzgerald
  • RE: PP Problems: External Standards, Arnold, James L. Jr.
  • RE: PP Problems: External Standards, Ken Elliott
  • Re: PP Problems: External Standards, NIAP Interpretations Board
• PP Problems: Requirement Refinement, Arnold, James L. Jr.
  • PP Problems: Requirement Refinement, Daniel P. Faigin
  • RE: PP Problems: Requirement Refinement, Arnold, James L. Jr.
  • Re: PP Problems: Requirement Refinement, NIAP Interpretations Board
• =?euc-kr?B?KLGksO0pILi2uf3AxyC/tb7ux9C9wCBEVkTHw7e5wMy+7ijBub73L8DUx9A=?= =?euc-kr?B?IMDMuqXGrik=?=, My0579
• Re: I-0463: Platform Inclusion In A TOE With FPT_SEP, NIAP Interpretations Board
  • RE: I-0463: Platform Inclusion In A TOE With FPT_SEP, Arnold, James L. Jr.
    • RE: I-0463: Platform Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
  • RE: I-0463: Platform Inclusion In A TOE With FPT_SEP, Arnold, James L. Jr.
    • RE: I-0463: Platform Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
• Re: How to use FTP_ITC (Inter-TSF trusted channel) ?, NIAP Interpretations Board
• Reminder: Please join us..., Bodacion Technologies
• CONFIDENTIAL BUSINESS RELATIONSHIP, sanusi_dagash
• Online Web Seminar: How to End Your Web Hacking Nightmares Forever*, Bodacion Technologies
• ST evaluation on threats and security objectives, YOKOTA HIROFUMI
  • Re: ST evaluation on threats and security objectives, Gary Stoneburner
    • Re: ST evaluation on threats and security objectives, YOKOTA HIROFUMI
      • Re: ST evaluation on threats and security objectives, Gary Stoneburner
      • Re: ST evaluation on threats and security objectives, YOKOTA HIROFUMI
      • Re: ST evaluation on threats and security objectives, Gary Stoneburner
      • Level of description on Security requirements for the IT environment, YOKOTA HIROFUMI
      • Re: Level of description on Security requirements for the IT environment, Gary Stoneburner
      • Re: Level of description on Security requirements for the IT environment, YOKOTA HIROFUMI
      • Re: Level of description on Security requirements for the IT environment, Gary Stoneburner
      • Re: Level of description on Security requirements for the IT environment, YOKOTA HIROFUMI
      • Re: Level of description on Security requirements for the IT environment, YOKOTA HIROFUMI
      • Re: Level of description on Security requirements for the IT environment, Gary Stoneburner
      • Re: ST evaluation on threats and security objectives, YOKOTA HIROFUMI
      • Re: ST evaluation on threats and security objectives, Gary Stoneburner
      • Re: ST evaluation on threats and security objectives, YOKOTA HIROFUMI
  • Re: ST evaluation on threats and security objectives, NIAP Interpretations Board
    • Re: ST evaluation on threats and security objectives, Dr.Ir. D.J. Out
      • I-417: Association Of Information Flow Attributes W/Subjects And Information, YOKOTA HIROFUMI
      • Re: I-417: Association Of Information Flow Attributes W/Subjects And Information, YOKOTA HIROFUMI
• =?euc-kr?B?KLGksO0pILOquLjAxyDAvb7HwLsgxu3B/cfSILz2IMDWtMIgu+e/7g==?= =?euc-kr?B?teXG7cH9seK4piC15biztM+02SEhIA==?=, =?euc-kr?B?u+e/7rXlwKfB7g==?=
• =?GB2312?B?xPqyu8HLveK1xLjfv8a8vKOs1f24+NPD1d+0+MC0xPqyu9aqtcA=?=, cc-conny
• New AVA families: EAL4 = EAL5, Gary Stoneburner
  • RE: New AVA families: EAL4 = EAL5, Arnold, James L. Jr.
  • RE: New AVA families: EAL4 = EAL5, Gary Stoneburner
• =?GB2312?B?udjQxL7N09DK1bvxo6G0+sDt0OjSqsTjztLL+6Oh?=, xiang123113
• =?euc-kr?B?KLGksO0pILXoseK4uCDH2LW1ILvswMwguvzB9rTCIMC9vsc=?=, =?euc-kr?B?x9jHx7vnv+615Q==?=
• FDP_IFC.1(Information flow control (Part2), YOKOTA HIROFUMI
  • Re: FDP_IFC.1(Information flow control (Part2), Gary Stoneburner
• CC conformance claim, YOKOTA HIROFUMI
  • Re: CC conformance claim, Gary Stoneburner
    • Re: CC conformance claim, YOKOTA HIROFUMI
      • Re: CC conformance claim, Gary Stoneburner
      • How to use FTP_ITC (Inter-TSF trusted channel) ?, YOKOTA HIROFUMI
  • CC conformance claim, YOKOTA HIROFUMI
  • Re: CC conformance claim, YOKOTA HIROFUMI
  • RE: CC conformance claim, Foreman, Elizabeth A.
  • RE: CC conformance claim, Foreman, Elizabeth A.
    • Re: CC conformance claim, YOKOTA HIROFUMI
    • Re: CC conformance claim, YOKOTA HIROFUMI
  • RE: CC conformance claim, Foreman, Elizabeth A.
• Could ST authors free to craft the organisational security policies?, YOKOTA HIROFUMI
  • Re: Could ST authors free to craft the organisational security policies?, Gary Stoneburner
  • Re: Could ST authors free to craft the organisational security policies?, NIAP Interpretations Board
• FDP_IFC.1(Information flow control), YOKOTA HIROFUMI
  • Re: FDP_IFC.1(Information flow control), Nir Naaman
    • Re: FDP_IFC.1(Information flow control), YOKOTA HIROFUMI
  • Re: FDP_IFC.1(Information flow control), Gary Stoneburner
  • Re: FDP_IFC.1(Information flow control), YOKOTA HIROFUMI
    • Re: FDP_IFC.1(Information flow control), Gary Stoneburner
  • FDP_IFC.1(Information flow control), YOKOTA HIROFUMI
• Å©¸®½º¸¶½º ¼±¹° ÃÊƯ°¡, ÀÎÅͳݾ˹ٳÝ
• =?gb2312?B?UkU6ID8/P6GqPz8/Pz8/Pz8/Pz8/Pz8=?=, Donna.Wessel
  • =?utf-8?Q?RE:_Possible_Spam_=2806.10/05.00=29:_R?= =?utf-8?Q?E:_=3F=3F=3F=C2=A1=C2=AA=3F=3F=3F=3F=3F=3F=3F=3F=3F=3F=3F=3F?= =?utf-8?Q?=3F=3F?=, Dragua Zenelaj
• =?big5?Q?FW:=A9=D0=AB=CE=B6U=B4=DA=C2=E0=B6U3.65%?=, PERRY_SCB
• ÀýÈ£ÀÇ Âù½º!! Å©¸®½º¸¶½º ¼±¹°·Î ¼îÇθô °¡Á®°¡¼¼¿ä, ¼îÇθô
• ¼îÇθô ¹«·á·Î ºÐ¾ç ¹Þ¾Æ°¡¼¼¿ä., ¸â¹ö¸ô(¹«Á¡Æ÷)
• =?GB2312?B?087KwL3noarKwL3n1qrKtrTz0M3NvMas1bnRsLXYx/i0+sDt?=, jock521
• =?GB2312?B?xOO1xLzSysehsMLMyauhsbXEwvCjvw==?=, tianxin
• I-0354/0417: Association Of Information Flow Attributes W/Subjects And Information, YOKOTA HIROFUMI
  • Re: I-0354/0417: Association Of Information Flow Attributes W/Subjects And Information, Gary Stoneburner
• What level of detail is appropriate in a statement of security objectives, YOKOTA HIROFUMI
  • Re: What level of detail is appropriate in a statement of security objectives, YOKOTA HIROFUMI
    • Re: What level of detail is appropriate in a statement of security objectives, Gary Stoneburner
• ¿µ¾î °øºÎ ½±°Ô Çϼ¼¿ä[±¤°í], es
• ÃÖ÷´Ü ºÎ¾÷À¸·Î 2003³âÀ» ¸ÂÀÌ Çϼ¼¿ä., ÀçÅþ˹ٳÝ
• ÷´Ü 2003³â Ãֽž˹٠Á¤º¸, ÀÎÅͳݾ˹ٳÝ
• Coverage of TSP and attributes (RI#144, RI#145), YOKOTA HIROFUMI
  • Re: Coverage of TSP and attributes (RI#144, RI#145), Gary Stoneburner
  • Re: Coverage of TSP and attributes (RI#144, RI#145), NIAP Interpretations Board
• »çÀ̹ö ÀçÅà ¾Ë¹Ù ½ÃÀÛÇϼ¼¿ä[3¸¸¿ø ¹Þ¾Æ°¡¼¼¿ä], ÀçÅþ˹ٳÝ
• expertise, resources, and motivation of attackers, YOKOTA HIROFUMI
  • Re: expertise, resources, and motivation of attackers, Gary Stoneburner
  • Re: expertise, resources, and motivation of attackers, YOKOTA HIROFUMI
    • Re: expertise, resources, and motivation of attackers, Gary Stoneburner
  • Re: Expertise, Resources, and Motivation of Attackers, NIAP Interpretations Board
  • RE: Expertise, Resources, and Motivation of Attackers, Arnold, James L. Jr.
    • RE: Expertise, Resources, and Motivation of Attackers, Daniel P. Faigin
  • RE: Expertise, Resources, and Motivation of Attackers, Hal W Forsberg
    • RE: Expertise, Resources, and Motivation of Attackers, Daniel P. Faigin
• =?euc-kr?B?KLGksO0pIL+suLu/rL3DIMDMuqXGrsC9vsfAuiC757/uteXAp8Hu?= =?euc-kr?B?sKEgw6XA08H2sNq9wLTPtNku?=, =?euc-kr?B?u+e/7rXlwKfB7g==?=
• TOE description (general terms), YOKOTA HIROFUMI
  • Re: TOE description (general terms), Gary Stoneburner
• FCS_COP assignment, YOKOTA HIROFUMI
  • Re: FCS_COP assignment, Gary Stoneburner
    • Re: FCS_COP assignment, YOKOTA HIROFUMI
  • FCS_COP assignment, YOKOTA HIROFUMI
  • FCS_COP assignment, YOKOTA HIROFUMI
    • Re: FCS_COP assignment, Gary Stoneburner
  • Re: FCS_COP assignment, YOKOTA HIROFUMI
    • Re: FCS_COP assignment, Gary Stoneburner
• FDP_DAU Versus FCO_NRO, YOKOTA HIROFUMI
  • Re: FDP_DAU Versus FCO_NRO, Gary Stoneburner
    • Re: FDP_DAU Versus FCO_NRO, YOKOTA HIROFUMI
      • Re: FDP_DAU Versus FCO_NRO, Gary Stoneburner
  • Re: FDP_DAU Versus FCO_NRO, NIAP Interpretations Board
• I-0453: TSF And Support Code, NIAP Interpretations Board
  • RE: I-0453: TSF And Support Code, Knoke, Jim
  • RE: I-0453: TSF And Support Code, Gary Stoneburner
  • RE: I-0453: TSF And Support Code, Knoke, Jim
    • Re: I-0453: TSF And Support Code, Nir Naaman
      • Re: I-0453: TSF And Support Code, Daniel P. Faigin
  • RE: I-0453: TSF And Support Code, Gary Stoneburner
  • Re: I-0453: TSF And Support Code, NIAP Interpretations Board
  • I-0453: TSF And Support Code, NIAP Interpretations Board
    • RE: I-0453: TSF And Support Code, Nir Naaman
      • Re: I-0453: TSF And Support Code, Franklin Haskell
  • RE: I-0453: TSF And Support Code, Shari Galitzer
    • RE: I-0453: TSF And Support Code, Daniel P. Faigin
  • Re: I-0453: TSF And Support Code, Hal W Forsberg
    • Re: I-0453: TSF And Support Code, Daniel P. Faigin
      • RE: I-0453: TSF And Support Code, Nir Naaman
      • RE: I-0453: TSF And Support Code, Daniel P. Faigin
      • RE: I-0453: TSF And Support Code, Gary Stoneburner
  • Re: I-0453: TSF And Support Code, NIAP Interpretations Board
  • I-0453: TSF And Support Code, NIAP Interpretations Board
    • RE: I-0453: TSF And Support Code, Nir Naaman
      • RE: I-0453: TSF And Support Code, Daniel P. Faigin
  • RE: I-0453: TSF And Support Code, Arnold, James L. Jr.
    • RE: I-0453: TSF And Support Code, Nir Naaman
  • Re: I-0453: TSF And Support Code, NIAP Interpretations Board
  • Re: I-0453: TSF And Support Code, NIAP Interpretations Board
• I-0432: List Of Subjects And Objects Refers To Types Thereof, NIAP Interpretations Board
  • Re: I-0432: List Of Subjects And Objects Refers To Types Thereof, NIAP Interpretations Board
• Re: ADV_FSP.1-6, NIAP Interpretations Board
• I-0392: AVA_MSU Does Not Mandate Extra Functions In The TOE, NIAP Interpretations Board
  • Re: I-0392: AVA_MSU Does Not Mandate Extra Functions In The TOE, NIAP Interpretations Board
• I-0461: Definition Of TSF: Relied Upon For The Correct Enforcement, NIAP Interpretations Board
  • RE: I-0461: Definition Of TSF: Relied Upon For The Correct Enforcement, Knoke, Jim
  • I-0461: Definition Of TSF: Relied Upon For The Correct Enforcement, NIAP Interpretations Board
  • Re: I-0461: Definition Of TSF: Relied Upon For The Correct Enforcement, NIAP Interpretations Board
  • Re: I-0461: Definition Of TSF: Relied Upon For The Correct Enforcement, NIAP Interpretations Board
• I-0451: When To Use IFF/IFC And ACC/ACF, NIAP Interpretations Board
  • RE: I-0451: When To Use IFF/IFC And ACC/ACF, Knoke, Jim
    • RE: I-0451: When To Use IFF/IFC And ACC/ACF, Daniel P. Faigin
• [ ±¤ °í ] °í°´´ÔÀÇ ´ëÃâ °¡´É»óÇ°Àº 31 °¡ÁöÀÔ´Ï´Ù. ½Å°³³ä ´ëÃâ¾È³»¼­ºñ½º ¿ÂÅ©·¹, ¿ÂÅ©·¹
• [±¤°í]¾ÆÁ÷µµ ¿µ¾î ¾î·Æ°Ô ¹è¿ì½Ã³ª¿ä?, FunEnglish
• To claim the protection from interference without FPT_SEP, YOKOTA HIROFUMI
  • Re: To claim the protection from interference without FPT_SEP, NIAP Interpretations Board
• Do we need trusted path/channel mandatory?, YOKOTA HIROFUMI
  • Do we need trusted path/channel mandatory?, YOKOTA HIROFUMI
  • Do we need trusted path/channel mandatory?, YOKOTA HIROFUMI
  • Re: Do we need trusted path/channel mandatory?, NIAP Interpretations Board
• (±¤°í) (¼ºÀα¤°í) Ä«µå ´ëÃâ ¿¬Ã¼°ü¸® ³¡³»¼¼¿ä,,¼ºÀÎÀÚ·á Çѹø¿¡ ¿©·¯½ÎÀÌÆ® ÀÌ¿ë¹æ¹ý..µîµî..¹«·áÀÚ·á ³ÑÃijª´Â°÷, ¸Ó´Ï °¡ ¸¹ÀÌ..¸Å´ÏÁ®
• (±¤°í) - ¸Å¿ù Ä«µå°ª¶§¹®¿¡ °í¹ÎÀ̽źи¸ º¸¼¼¿ä..±ÝÀ¶,Ä«µåÁ¤º¸ ½º½º·ÎÇϱâ - ¹«¼ö¼ö·á, Ä«µå´ëÃ⽺Äð
• (±¤°í) - Àý´ë ÀÐÁö ¸¶¼¼¿ä...Á¤¸» Áß¿äÇÑ Á¤º¸ÀÔ´Ï´Ù., ´ëÃâ¸Å´ÏÁ®
• (±¤°í) - ½Å¿ëÁÖÀÇ.±ÝÀ¶Ä«µåÀÇ °üÇÑ ¸ðµç Á¤º¸...200¿©°¡Áö.¹«·áÁ¦°ø, ´ëÃâ¸Å´ÏÁ®
• [°µÈ¨±¤°í] ¼ºÀο±±âÀÚ·áµé ¸ð¾Ò½À´Ï´Ù. (19¼¼ÀÌÇÏ ÃâÀÔ±ÝÁö), ½Å¹Ì¸²
• Can only part of the HW be included in the TSF?, Knoke, Jim
  • Can only part of the HW be included in the TSF?, Daniel P. Faigin
    • Re: Can only part of the HW be included in the TSF?, Nir Naaman
  • RE: Can only part of the HW be included in the TSF?, J. David Thompson (CygnaCom)
    • RE: Can only part of the HW be included in the TSF?, Daniel P. Faigin
  • RE: Can only part of the HW be included in the TSF?, J. David Thompson (CygnaCom)
    • RE: Can only part of the HW be included in the TSF?, Daniel P. Faigin
  • RE: Can only part of the HW be included in the TSF?, J. David Thompson (CygnaCom)
    • Re: Can only part of the HW be included in the TSF?, James Donndelinger
  • RE: Can only part of the HW be included in the TSF?, J. David Thompson (CygnaCom)
  • RE: Can only part of the HW be included in the TSF?, Knoke, Jim
  • RE: Can only part of the HW be included in the TSF?, Knoke, Jim
  • Re: Can only part of the HW be included in the TSF?, NIAP Interpretations Board
• Internal TOE Transfer Protection, Nir Naaman
  • Re: Internal TOE Transfer Protection, Nir Naaman
    • Re: Internal TOE Transfer Protection, James Donndelinger
  • RE: Internal TOE Transfer Protection, J. David Thompson (CygnaCom)
  • Re: Internal TOE Transfer Protection, YOKOTA HIROFUMI
  • Re: Internal TOE Transfer Protection, NIAP Interpretations Board
• ADV_FSP.1-6 ..., Alexander Henefield
• Re: REQUEST FOR QUOTATION PALLADIUM MODEM, luxorgoods
• Re: TOE Security Policy Model, NIAP Interpretations Board
  • RE: TOE Security Policy Model, Ata, John
    • RE: TOE Security Policy Model, Daniel P. Faigin
  • Re: TOE Security Policy Model, NIAP Interpretations Board
  • RE: TOE Security Policy Model, Ata, John
• Introduction to CC-CMT Mailings, NIAP Interpretations Board
• RI: when must abstract machine and self-test tests run?, Knoke, Jim
  • Re: RI: when must abstract machine and self-test tests run?, NIAP Interpretations Board
• Nuke ALC_DVS.1.2C, Knoke, Jim
  • Re: Nuke ALC_DVS.1.2C, NIAP Interpretations Board
• Does TSF include administrator?, Knoke, Jim
  • Re: Does TSF include administrator?, Jeff Gilliatt
• I-0459 Approved, NIAP Interpretations Board
• Re: I-0347: Including Sensitive Information In Audit Records, NIAP Interpretations Board
  • Re: I-0347: Including Sensitive Information In Audit Records, Tim Bergendahl
  • Re: I-0347: Including Sensitive Information In Audit Records, NIAP Interpretations Board
  • Re: I-0347: Including Sensitive Information In Audit Records, NIAP Interpretations Board
• I-0388: What Is The Difference Between "Sort" And "Order"?, NIAP Interpretations Board
  • Re: I-0388: What Is The Difference Between "Sort" And "Order"?, Jerome F. Myers
    • Re: I-0388: What Is The Difference Between "Sort" And "Order"?, Tim Bergendahl
  • Re: I-0388: What Is The Difference Between "Sort" And "Order"?, NIAP Interpretations Board
  • Re: I-0388: What Is The Difference Between "Sort" And "Order"?, NIAP Interpretations Board
• I-0463: Hardware Inclusion In A TOE With FPT_SEP, NIAP Interpretations Board
  • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Tim Bergendahl
  • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Arnold, James L. Jr.
    • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
  • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Arnold, James L. Jr.
    • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
      • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Nir Naaman
      • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
  • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Arnold, James L. Jr.
    • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
  • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Arnold, James L. Jr.
    • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
  • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, NIAP Interpretations Board
  • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, NIAP Interpretations Board
  • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, NIAP Interpretations Board
  • RE: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Knoke, Jim
  • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, NIAP Interpretations Board
• NIB Posting Introduction, NIAP Interpretations Board
• Testing allowed by privileged programs?, Knoke, Jim
  • Re: Testing allowed by privileged programs?, NIAP Interpretations Board
• RI: data import and export using operator guidance, Knoke, Jim
  • Re: RI: data import and export using operator guidance, NIAP Interpretations Board
• Satisfying requirements trivially, Knoke, Jim
  • Re: Satisfying requirements trivially, NIAP Interpretations Board
  • RE: Satisfying requirements trivially, Knoke, Jim
  • Re: Satisfying requirements trivially, NIAP Interpretations Board
• RI: "parts" of the TOE, Knoke, Jim
  • Re: RI: "parts" of the TOE, NIAP Interpretations Board
• NIAP-0375 ..., Alexander Henefield
  • Re: NIAP-0375 ..., NIAP Interpretations Board
• TOE Security Policy Model ..., Trey Henefield
• CC Request for Interpretation: pseudo-code and TSP-enforcing functions, Knoke, Jim
• RE: CC request for interpretation: TSF required during maintenanc e mode?, McEvilley, Michael
• I-0459: CM Systems May Have Varying Degrees Of Rigor And Function, NIAP Interpretations Board
  • I-0459: CM Systems May Have Varying Degrees Of Rigor And Function, NIAP Interpretations Board
• Re: Request for interpretation: treatment of hardware needed by software product, NIAP Interpretations Board
  • Re: Request for interpretation: treatment of hardware needed bysoftware product, James Arnold
    • Re: Request for interpretation: treatment of hardware needed bysoftware product, Gary Stoneburner
  • RE: Request for interpretation: treatment of hardware needed by software product, Knoke, Jim
    • RE: Request for interpretation: treatment of hardware needed by software product, Daniel P. Faigin
  • RE: Request for interpretation: treatment of hardware needed by software product, Arnold, James L. Jr.
    • RE: Request for interpretation: treatment of hardware needed by software product, Daniel P. Faigin
  • RE: Request for interpretation: treatment of hardware needed by software product, Knoke, Jim
    • RE: Request for interpretation: treatment of hardware needed by software product, Daniel P. Faigin
  • RE: Request for interpretation: treatment of hardware needed by software product, Arnold, James L. Jr.
    • RE: Request for interpretation: treatment of hardware needed by software product, Daniel P. Faigin
  • RE: Request for interpretation: treatment of hardware needed by software product, Arnold, James L. Jr.
    • RE: Request for interpretation: treatment of hardware needed by software product, Daniel P. Faigin
      • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Nir Naaman
      • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
      • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Nir Naaman
      • Re: I-0463: Hardware Inclusion In A TOE With FPT_SEP, Daniel P. Faigin
  • Re: Request for interpretation: treatment of hardware needed by software product, NIAP Interpretations Board
  • Re: Request for interpretation: treatment of hardware needed by software product, NIAP Interpretations Board
• Re: Possible request for interpretation: low-level design doc questions, NIAP Interpretations Board
  • RE: Possible request for interpretation: low-level design doc questions, Knoke, Jim
  • Re: Possible request for interpretation: low-level design doc questions, NIAP Interpretations Board
• NIB Status Report, NIAP Interpretations Board
• I-0460: Empty Selections Or Assignments/One Or More, NIAP Interpretations Board
  • Re: I-0460: Empty Selections Or Assignments/One Or More, Jim Brosey
    • Re: I-0460: Empty Selections Or Assignments/One Or More, Elizabeth A. Foreman
  • Re: I-0460: Empty Selections Or Assignments/One Or More, James Arnold
  • RE: I-0460: Empty Selections Or Assignments/One Or More, Gary Grainger
  • I-0460: Empty Selections Or Assignments/One Or More, NIAP Interpretations Board
    • Re: I-0460: Empty Selections Or Assignments/One Or More, Tim Bergendahl
  • Re: I-0460: Empty Selections Or Assignments/One Or More, NIAP Interpretations Board
  • RE: I-0460: Empty Selections Or Assignments/One Or More, Arnold, James L. Jr.
    • RE: I-0460: Empty Selections Or Assignments/One Or More, Daniel P. Faigin
  • RE: I-0460: Empty Selections Or Assignments/One Or More, J. David Thompson (CygnaCom)
    • Re: I-0460: Empty Selections Or Assignments/One Or More, Jeff Gilliatt
  • Re: I-0460: Empty Selections Or Assignments/One Or More, NIAP Interpretations Board
• Re: I-0350: Clarification Of Resources/Objects For Residual Information Protection, NIAP Interpretations Board
• Re: CC request for interpretation: TSF required during maintenance mode?, NIAP Interpretations Board
  • Re: CC request for interpretation: TSF required during maintenance mode?, NIAP Interpretations Board
• guidance for AMP, LI tian
  • Re: Guidance for AMP, NIAP Interpretations Board
• RE: low-level design doc questions (what's in the TSF?), Knoke, Jim
  • RE: low-level design doc questions (what's in the TSF?), Gary Stoneburner
  • RE: low-level design doc questions (what's in the TSF?), Knoke, Jim
  • Re: low-level design doc questions (what's in the TSF?), NIAP Interpretations Board
• I-0350 APPROVED: Clarification Of Resources/Objects For Residual Information Protection, NIAP Interpretations Board
• I-0381 APPROVED: Relationship Between FPT_PHP And FMT_MOF, NIAP Interpretations Board
• I-0415 APPROVED: User Attributes To Be Bound Should Be Specified, NIAP Interpretations Board
• RE: CC request for interpretation: TSF required during maintenanc e mo de?, McEvilley, Michael
• Purpose and Use of the cc-cmt List, NIAP Interpretations Board
  • Re: Purpose and Use of the cc-cmt List, James Arnold
    • Re: Purpose and Use of the cc-cmt List, Daniel P. Faigin
• suscribe, Rodriguez.Paula
• Homeland Defense Journal Issue #2 Available for Download, David Dickson - HDJ Distribution
• Comment on Boundary Gateway VPN PP Draft, Shari Galitzer
  • Re: Comment on Boundary Gateway VPN PP Draft, NIAP Interpretations Board
• Where to submit questions or concerns on drafts, Shari Galitzer
• UNSUBSCRIBE, Gill.William
  • unsubscribe, Alex Ragen
• Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, NIAP Interpretations Board
  • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, James Arnold
  • Re:I-0356: FDP_RIP Annex: Reuse of Subject Data Notes, NIAP Interpretations Board
    • Re: I-0356: FDP_RIP Annex: Reuse of Subject Data Notes, James Arnold
  • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, NIAP Interpretations Board
  • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Knoke, Jim
  • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, NIAP Interpretations Board
  • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Arnold, James L. Jr.
    • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Daniel P. Faigin
  • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Arnold, James L. Jr.
    • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Daniel P. Faigin
  • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Arnold, James L. Jr.
    • RE: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Daniel P. Faigin
    • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, Nir Naaman
  • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, NIAP Interpretations Board
  • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, NIAP Interpretations Board
  • Re: I-0356: FDP_RIP Annex: Reuse Of Subject Data Notes, NIAP Interpretations Board
• Introduction to CC-CMTJanuary 2002 Mailings, NIAP Interpretations Board
• Bioterrorism, Chem - Bio, Weapons of Mass Destruction Training Conference, David C. Dickson
• Performance Based Contracting Training Conference, David C. Dickson
• Premier Issue - Homeland Defense Journal, David C. Dickson
• Homeland Security Journal, Combs.Jim
• CALENDAR OF EVENTS, David C. Dickson
• SUBSCRIBE, Simpson, Randy
  • SUBSCRIBE, Charles
  • SUBSCRIBE, Bower, Michael
  • SUBSCRIBE, Lewis, Alton W
    • SUBSCRIBE, Daniel P. Faigin
  • SUBSCRIBE, Olson, Paul A.
    • SUBSCRIBE, Dave Parrish
  • Subscribe, Roland Mueller
  • SUBSCRIBE, Gill.William
  • SUBSCRIBE, Brennan.Beverly
  • SUBSCRIBE, Worster.Carl
  • SUBSCRIBE, Williams.Joyce
  • SUBSCRIBE, Kerner.Ken
• Homeland Defense Journal - Subscription available - See below for content info, David C. Dickson
  • Subscribe, Charles
• CYBER Security Training Conference - Dec 18, 2001 - Wash DC, David C. Dickson
• Mobile & Wireless Training Conf. - **** New Speakers Added **** Dec 11, 2001, David C. Dickson
• Homeland Defense Training Conf - CYBER Security - Dec 18, 2001 - Wash DC -, David C. Dickson
• Homeland Defense Training Conf. - Mobile & Wireless - Dec 11, 2001 - Wash DC, David C. Dickson
• CC process question: security measures during TOE development, Knoke, Jim
  • Re: CC process question: security measures during TOE development, NIAP Interpretations Board
    • NIB responses to cc-cmt questions, James Arnold
      • NIB responses to cc-cmt questions, Daniel P. Faigin
• CC request for interpretation: configuration item granularity, Knoke, Jim
  • Re: CC request for interpretation: configuration item granularity, NIAP Interpretations Board
• CC request for interpretation: CM automation, Knoke, Jim
  • Re: CC request for interpretation: CM automation, NIAP Interpretations Board
• CC request for interpretation: TSF required during maintenance mo de?, Knoke, Jim
  • Re: CC request for interpretation: TSF required during maintenance mo de?, NIAP Interpretations Board
    • Re: CC request for interpretation: TSF required during maintenance mo de?, James Arnold
• CC request for interpretation: are tests part of TSF?, Knoke, Jim
  • Re: CC request for interpretation: are tests part of TSF?, NIAP Interpretations Board
    • Re: CC request for interpretation: are tests part of TSF?, James Arnold
  • Re: CC request for interpretation: are tests part of TSF?, NIAP Interpretations Board
    • Re: CC request for interpretation: are tests part of TSF?, James Arnold
  • RE: CC request for interpretation: are tests part of TSF?, Knoke, Jim
  • Re: CC request for interpretation: are tests part of TSF?, NIAP Interpretations Board
• CC request for interpretation: testing while in normal mode?, Knoke, Jim
  • Re: CC request for interpretation: testing while in normal mode?, NIAP Interpretations Board
    • Re: CC request for interpretation: testing while in normal mode?, James Arnold
      • Re: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
      • Re: CC request for interpretation: testing while in normal mode?, James Arnold
  • RE: CC request for interpretation: testing while in normal mode?, McEvilley, Michael
    • RE: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
  • RE: CC request for interpretation: testing while in normal mode?, McEvilley, Michael
    • RE: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
      • Re: CC request for interpretation: testing while in normal mode?, James Arnold
  • RE: CC request for interpretation: testing while in normal mode?, McEvilley, Michael
    • RE: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
  • RE: CC request for interpretation: testing while in normal mode?, McEvilley, Michael
    • Re: CC request for interpretation: testing while in normal mode?, James Arnold
      • Re: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
      • Re: CC request for interpretation: testing while in normal mode?, James Arnold
      • Re: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
      • Re: CC request for interpretation: testing while in normal mode?, James Arnold
      • Re: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
      • What is the TSF?, James Donndelinger
  • RE: CC request for interpretation: testing while in normal mode?, McEvilley, Michael
    • RE: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
    • Re: CC request for interpretation: testing while in normal mode?, James Arnold
      • Re: CC request for interpretation: testing while in normal mode?, Daniel P. Faigin
      • Re: CC request for interpretation: testing while in normal mode?, Michael McEvilley - Home
  • RE: CC request for interpretation: testing while in normal mode?, Ata, John
  • Re: CC request for interpretation: testing while in normal mode?, NIAP Interpretations Board
  • RE: CC request for interpretation: testing while in normal mode?, Knoke, Jim
  • Re: CC request for interpretation: testing while in normal mode?, NIAP Interpretations Board
  • RE: CC request for interpretation: testing while in normal mode?, Knoke, Jim
  • Re: CC request for interpretation: testing while in normal mode?, NIAP Interpretations Board
• CC request for interpretation: immutable audit ID, Knoke, Jim
  • Re: CC request for interpretation: immutable audit ID, NIAP Interpretations Board
    • Re: CC request for interpretation: immutable audit ID, James Arnold
  • Re: CC request for interpretation: immutable audit ID, NIAP Interpretations Board
• Request for interpretation: treatment of hardware needed by softw are product, Knoke, Jim
  • Re: Request for interpretation: treatment of hardware needed by softw are product, NIAP Interpretations Board
    • Re: Request for interpretation: treatment of hardware needed by softw are product, James Arnold
• Request for interpretation: TSF partitioning, Knoke, Jim
  • Re: Request for interpretation: TSF partitioning, NIAP Interpretations Board
    • Re: Request for interpretation: TSF partitioning, James Arnold
  • Re: Request for interpretation: TSF partitioning, NIAP Interpretations Board
• Process question: evaluation without PP, Knoke, Jim
• Possible request for interpretation: low-level design doc questio ns, Knoke, Jim
  • Re: Possible request for interpretation: low-level design doc questio ns, NIAP Interpretations Board
    • Re: Possible request for interpretation: low-level design doc questio ns, James Arnold
      • Re: Possible request for interpretation: low-level design doc questio ns, Daniel P. Faigin
      • Re: Possible request for interpretation: low-level design doc questio ns, James Arnold
      • Re: Possible request for interpretation: low-level design doc questio ns, Daniel P. Faigin
• I-0381: Relationship Between FPT_PHP And FMT_MOF, Interpretations Working Group
  • Re: I-0381: Relationship Between FPT_PHP And FMT_MOF, NIAP Interpretations Board
• I-0414: Site-Configurable Prevention Of Audit Loss, Interpretations Working Group
  • I-0414: Site-Configurable Prevention Of Audit Loss, Arnold, James L. Jr.
    • Re: I-0414: Site-Configurable Prevention Of Audit Loss, Dr.Ir. D.J. Out
      • Handling of a final interpretation, YOKOTA HIROFUMI
  • Re: I-0414: Site-Configurable Prevention Of Audit Loss, NIAP Interpretations Board
• Introduction to August 2001 Interpretation Mailing, Interpretations Working Group
• * Re: I-0420 Attribute Inheritance/Modification Rules Need To Be Included In Policy, Interpretations Working Group
• Mail to the NIAP Interpretations Board, Interpretations Working Group
• Re: I-0420 Attribute Inheritance/Modification Rules Need To Be Included In Policy, Interpretations Working Group
• I-0420: Attribute Inheritance/Modification Rules Need To Be Included In Policy, Interpretations Working Group
  • Re: I-0420: Attribute Inheritance/Modification Rules Need To Be Included In Policy, NIAP Interpretations Board
  • Re: I-0420: Attribute Inheritance/Modification Rules Need To Be Included In Policy, NIAP Interpretations Board
• I-0367: Management Sections Are Informative, Interpretations Working Group
• I-0350: Clarification Of Resources/Objects For Residual Information Protection, Interpretations Working Group
  • I-0350: Clarification Of Resources/Objects For Residual Information Protection, Interpretations Working Group
  • I-0350: Clarification Of Resources/Objects For Residual Information Protection, Interpretations Working Group
  • Re: I-0350: Clarification Of Resources/Objects For Residual Information Protection, NIAP Interpretations Board
    • Re: I-0350: Clarification Of Resources/Objects For Residual Information Protection, James Arnold
• I-0410: Auditing Of Subject Identity For Unsuccessful Logins, Interpretations Working Group
  • Re: I-0407: Empty Selections Or Assignments, Daniel P. Faigin
  • I-0410: Auditing Of Subject Identity For Unsuccessful Logins, Interpretations Working Group
• I-0429: Selecting One Or More, Interpretations Working Group
  • I-0429: Selecting One Or More, Interpretations Working Group
  • I-0429: Selecting One Or More, Interpretations Working Group
• Re: I-0338: Configuration Items In The Absence Of Explicit Scope, Interpretations Working Group
• Re: I-0413: Assurance Of RVM Is By Testing And Design, Interpretations Working Group
• Re: I-0339: Assurance Of RVM Is By Testing And Design Analysis, Interpretations Working Group
• I-0338: Configuration Items In The Absence Of Explicit Scope (Rescind Proposal), Interpretations Working Group
  • Re: I-0338: Configuration Items In The Absence Of Explicit Scope (Rescind Proposal), Mike Allen
    • Re: I-0338: Configuration Items In The Absence Of Explicit Scope (Rescind Proposal), Daniel P. Faigin
• I-0414: Method Of Audit Prevention May Be Site-Configurable, Interpretations Working Group
  • I-0414: Method Of Audit Prevention May Be Site-Configurable, Interpretations Working Group
• I-0438: Lack Of Integration Guidance, Interpretations Working Group
  • Re: I-0438: Lack Of Integration Guidance, Interpretations Working Group
  • I-0438: Lack Of Integration Guidance, Interpretations Working Group
  • I-0438: Lack Of Integration Guidance, Interpretations Working Group
• I-0412: Configuration Items In The Absence Of Configuration Management, Interpretations Working Group
  • I-0412: Configuration Items In The Absence Of Configuration Management, Interpretations Working Group
• I-0409: Other Properties In FMT_MSA.3 Should Be Specified By Assignment, Interpretations Working Group
  • I-0409: Other Properties In FMT_MSA.3 Should Be Specified By Assignment, Interpretations Working Group
• Introduction to April 2001 Interpretation Mailing, Interpretations Working Group
• Continued use of Gibraltar for mirroring cc-cmt postings, Interpretations Working Group
• I-0427: Identification Of Standards, Interpretations Working Group
  • Re: I-0427: Identification Of Standards, Interpretations Working Group
  • Re: I-0427: Identification Of Standards, Interpretations Working Group
• I-0415: User Attributes To Be Bound Should Be Specified, Interpretations Working Group
  • Re: I-0415: User Attributes To Be Bound Should Be Specified, Interpretations Working Group
  • I-0415: User Attributes To Be Bound Should Be Specified, Interpretations Working Group
  • Re: I-0415: User Attributes To Be Bound Should Be Specified, NIAP Interpretations Board
• Queue Entries sent to management without changes, Interpretations Working Group
• I-0421: Application Notes In Protection Profiles Are Informative Only, Interpretations Working Group
  • Re: I-0421: Application Notes In Protection Profiles Are Informative Only, Interpretations Working Group
  • I-0421: Application Notes In Protection Profiles Are Informative Only, Interpretations Working Group
• Re: I-0393: A Completely Evaluated ST Is Not Required At The Start Of Evaluation, Interpretations Working Group
• What exactly is being interpreted?, James Arnold
  • Re: What exactly is being interpreted?, Gary Stoneburner
    • Re: What exactly is being interpreted?, James Arnold
      • Re: What exactly is being interpreted?, Gary Stoneburner
• Re: I-0393: A Completely Evaluated ST Is Not Required When TOE Evaluation Starts, James Arnold
• Re: I-0369: Security Management Functions To Be Provided Must Be Enumerated, James Arnold
• Re: I-0407: Empty Selection Or Assignments, James Arnold
• U.S. NATIONAL INTERPRETATION PROCESS: WHAT IS IT ALL ABOUT?, James Arnold
• I-0382: TSF Architectural Protections Are Really Assurances, Interpretations Working Group
  • Re: I-0382: TSF Architectural Protections Are Really Assurances, James Arnold
  • Re: I-0382: TSF Architectural Protections Are Really Assurances, Interpretations Working Group
• I-0389: Recovery To A Known State, Interpretations Working Group
  • Re: I-0389: Recovery To A Known State, Interpretations Working Group
• I-0406: Automated Or Manual Recovery Is Acceptable, Interpretations Working Group
  • I-0406: Automated Or Manual Recovery Is Acceptable, Interpretations Working Group
• I-0393: A Completely Evaluated ST Is Not Required When TOE Evaluation Starts, Interpretations Working Group
• I-0397: Iteration On Assurance Components/Elements, Interpretations Working Group
• I-0413: Assurance Of RVM Is By Testing And Design Analysis, Interpretations Working Group
  • Re: I-0413: Assurance Of RVM Is By Testing And Design Analysis, James Arnold
  • Re: I-0413: Assurance Of RVM Is By Testing And Design Analysis, Interpretations Working Group
• I-0407: Empty Selections Or Assignments, Interpretations Working Group
  • Re: I-0407: Empty Selections Or Assignments, Interpretations Working Group
  • Re: I-0407: Empty Selections Or Assignments, Interpretations Working Group
  • Re: I-0407: Empty Selections Or Assignments, Interpretations Working Group
  • Re: I-0407: Empty Selections Or Assignments, Daniel P. Faigin
  • I-0407: Empty Selections Or Assignments, Interpretations Working Group
• Introduction to Proposed Interpretation Mailing, Interpretations Working Group
  • Introduction to Proposed Interpretation Mailing, Interpretations Working Group
  • Introduction to Proposed Interpretation Mailing, Interpretations Working Group
• LABELING CONVENTION IN NIAP INTERPRETATIONS, IWG
• Re: I-0352: Rules Governing Binding Should Be Specifyable, Interpretations Working Group
• I-0423: Some Modifications To The Audit Trail Are Authorized, Interpretations Working Group
• I-0405: American English Is An Acceptable Refinement, Interpretations Working Group
• I-0417: Association Of Information Flow Attributes W/Subjects And Information, Interpretations Working Group
• I-0375: Elements Requiring Authentication Mechanism, Interpretations Working Group
  • I-0375: Elements Requiring Authentication Mechanism, Interpretations Working Group
  • Re: I-0375: Elements Requiring Authentication Mechanism, James Arnold
  • Re: I-0375: Elements Requiring Authentication Mechanism, Interpretations Working Group
• I-0411: Guidance Includes AGD_ADM, ADG_USR, ADO, And ALC_FLR, Interpretations Working Group
• I-0369: Security Management Functions To Be Provided Must Be Enumerated, Interpretations Working Group
  • I-0369: Security Management Functions To Be Provided Must Be Enumerated, Interpretations Working Group
  • Re: I-0369: Security Management Functions To Be Provided Must Be Enumerated, Interpretations Working Group
• I-0387: Auditing Of Audit Storage Failures, Interpretations Working Group
  • I-0387: Auditing Of Audit Storage Failures, Interpretations Working Group
  • Re: I-0387: Auditing Of Audit Storage Failures, James Arnold
    • Re: I-0387: Auditing Of Audit Storage Failures, Daniel P. Faigin
    • Re: I-0387: Auditing Of Audit Storage Failures, Daniel P. Faigin
  • I-0387: Auditing Of Audit Storage Failures, Interpretations Working Group
  • Re: I-0387: Auditing Of Audit Storage Failures, NIAP Interpretations Board
  • Re: I-0387: Auditing Of Audit Storage Failures, NIAP Interpretations Board
  • RE: I-0387: Auditing Of Audit Storage Failures, Arnold, James L. Jr.
  • Re: I-0387: Auditing Of Audit Storage Failures, NIAP Interpretations Board
  • Re: I-0387: Auditing Of Audit Storage Failures, NIAP Interpretations Board
• I-0395: Security Attributes Include Attributes Of Information And Resources, Interpretations Working Group
  • I-0395: Security Attributes Include Attributes Of Information And Resources, Interpretations Working Group
• Re: I-0394: Iteration Must Cover All Scopes, Interpretations Working Group
• Welcome to CC-CMT, Interpretations Working Group
• Gary's Test, Monaco, Stephen M.
• cc-cmt@nist.gov - html and attachment test, Gary Stoneburner
  • Re: cc-cmt@nist.gov - html this time :-), Gary Stoneburner
• SMM-Test, Monaco, Stephen M.
• cc-cmt subscribe, Monaco, Stephen M.
• Initial test message, Gary Stoneburner

Problems or questions? Contact list-master@nist.gov