ic10:RequireSecureHardwareStorage

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: IMI 1.1 CD1
    • Component/s: Schema, Spec
    • None
    • Hide

      Optionally define a new namespace in the spec or reuse ic09:
      ic10 http://docs.oasis-open.org/imi/ns/identity-201010

      Proposal to define a new element:
      <xs:element name="RequireSecureHardwareStorage" type="tns:PolicyAssertionType" />

      PolicyAssertionType is already defined:
      <xs:complexType name="PolicyAssertionType">
      <xs:sequence>
      <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax" />
      </xs:sequence>
      <xs:anyAttribute namespace="##any" processContents="lax" />
      </xs:complexType>

      Proposal to add RequireSecureHardwareStorage to the 1.1 spec as a valid extension to InformationCardType in section "4 New ic:InformationCard elements"

      4.3 RequireSecureHardwareStorage
      <xs:element name="RequireSecureHardwareStorage"
      type="tns: SecureHardwareStoragePolicyType" />
      <xs:complexType name=" SecureHardwareStoragePolicyType">
      <xs:sequence>
      <xs:element name="NeverRevealMasterKey" type="xs:boolean" minOccurs="0"/>
      <xs:any namespace="##other" processContents="lax" minOccurs="0"
      maxOccurs="unbounded"/>
      </xs:sequence>
      </xs:complexType>

      ic:InformationCard\ic09: RequireSecureHardwareStorage
      This OPTIONAL element requests that the InformationCardPrivateData be stored on a secure hardware device. An example for a secure hardware is a smartcard.
      If NeverRevealMasterKey is present and its value is true then the MasterKey MUST be generated on the secure hardware and must never leave the hardware. All algorithms that require the MasterKey as input must be implemented on the hardware.

      Show
      Optionally define a new namespace in the spec or reuse ic09: ic10 http://docs.oasis-open.org/imi/ns/identity-201010 Proposal to define a new element: <xs:element name="RequireSecureHardwareStorage" type="tns:PolicyAssertionType" /> PolicyAssertionType is already defined: <xs:complexType name="PolicyAssertionType"> <xs:sequence> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax" /> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax" /> </xs:complexType> Proposal to add RequireSecureHardwareStorage to the 1.1 spec as a valid extension to InformationCardType in section "4 New ic:InformationCard elements" 4.3 RequireSecureHardwareStorage <xs:element name="RequireSecureHardwareStorage" type="tns: SecureHardwareStoragePolicyType" /> <xs:complexType name=" SecureHardwareStoragePolicyType"> <xs:sequence> <xs:element name="NeverRevealMasterKey" type="xs:boolean" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> ic:InformationCard\ic09: RequireSecureHardwareStorage This OPTIONAL element requests that the InformationCardPrivateData be stored on a secure hardware device. An example for a secure hardware is a smartcard. If NeverRevealMasterKey is present and its value is true then the MasterKey MUST be generated on the secure hardware and must never leave the hardware. All algorithms that require the MasterKey as input must be implemented on the hardware.

      The issuer of a card should be able to require storage of the card private data on a secure hardware.

            Assignee:
            Unassigned
            Reporter:
            Axel Nennker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: