Search results

Jump to: navigation, search
  • '''Title''': SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES '''Category''': Security Requirements Standard
    3 KB (379 words) - 03:58, 28 June 2018
  • '''Title''': Derived Test Requirements for FIPS PUB 140-2, Security Requirements for Cryptographic Modules ...S 140-2 and a framework for testing whether implementations conform to the standard. Every assertion from FIPS 140-2 is identified and given a requirement num
    589 B (82 words) - 03:58, 28 June 2018
  • '''Category''': Credential Requirements Specification '''Description''': Specifies the architectural and technical requirements for the Personal Identity Verification (PIV) card
    1 KB (173 words) - 03:58, 28 June 2018
  • '''Category''': Credential Requirements Specification '''Description''': Specifies the architectural and technical requirements for the Personal Identity Verification (PIV) card
    3 KB (374 words) - 00:25, 24 August 2020
  • **Chat from Paul Knight: Please also add brief entry per standard in Standards Inventory list at https://wiki.idesg.org/wiki/index.php?title= (note the "Add Standard" button there. The other two standards will be submitted shortly by Mary, I
    3 KB (532 words) - 03:58, 28 June 2018
  • ...unreasonable. If there are the IDEF requirements, then you have additional requirements based on the trust mark you are planning to use. **For things were we don’t have requirements, we should be using “should.”
    5 KB (760 words) - 03:58, 28 June 2018
  • <center>'''National Security Telecom Advisory Comm.(NSTAC) Report to the President on Identity Managemen <center>'''Oasis: Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0'''</center>
    845 KB (86,833 words) - 04:00, 28 June 2018
  • <center>'''National Security Telecom Advisory Comm.(NSTAC) Report to the President on Identity Managemen <center>'''Oasis: Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0'''</center>
    135 KB (15,051 words) - 04:00, 28 June 2018
  • ==== SECURITY CONTROL ==== ...rds employed within an entity to ensure compliance with applicable privacy requirements and manage privacy risks.
    11 KB (1,496 words) - 23:48, 5 September 2020
  • ...e-Requirement-v1.0-with-Supplemental-Guidance.pdf IDEF Baseline Functional Requirements and Supplemental Guidance v1.0]] :* NIST 800-63-2 (Standard approval)
    5 KB (599 words) - 04:00, 28 June 2018
  • '''Description''': A standard framework for Certificate Policies (CPs) and Certification Practice Stateme document is intended to provide a structure but not the requirements for what the policies should be. A
    2 KB (297 words) - 04:00, 28 June 2018
  • '''Category''': Document Development Standard introduction, scope, references, terms and definitions, and (optionally) requirements. Attention is paid to
    2 KB (217 words) - 04:00, 28 June 2018
  • ...ity objectives and controls in ISO/IEC 27002, is to create a common set of security categories and controls that can be implemented by a public cloud computing ...technically and might increase risks to those physical and logical network security controls in place.
    4 KB (531 words) - 04:00, 28 June 2018
  • '''Title''': ISO/IEC 29100:2011 Information technology -- Security techniques -- Privacy framework '''Description''': This International Standard provides a high-level framework for the protection of personally identifiab
    1,022 B (130 words) - 04:00, 28 June 2018
  • ...ology -- Security Techniques -- Information security management systems -- Requirements (ISO 27001) '''Category''': Security
    2 KB (270 words) - 04:00, 28 June 2018
  • .../index.php?title=Baseline_Functional_Requirements_v1.0 Baseline Functional Requirements v1.0 (BFR)]. ...dations] were published in 1984 (Red Book). They were designed to become a standard for identifying users, but that role has been assumed by internet email add
    56 KB (9,154 words) - 00:16, 30 October 2020
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== ** Plenary planning for Security Committee breakout
    4 KB (617 words) - 04:01, 28 June 2018
  • **ISO 29115 the Security Committee had already submitted this standard to the Standards Committee. ...OK to include if there are no endorsement of products. We have a minimum standard for quality and it has to help people in a more general way. Mary will add
    3 KB (460 words) - 04:01, 28 June 2018
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== * Plenary planning for Security Committee breakout
    3 KB (481 words) - 04:01, 28 June 2018
  • ==SECURITY COMMITTEE MEETING NOTES - '''''draft'''''== ...ry is being worked: the FMO will provide an update on the cross committee requirements, a number of mini sessions are being planned, updates from pilots and a goo
    4 KB (609 words) - 04:01, 28 June 2018

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)