OID reference

cpkiMIB

1.3.6.1.4.1.9.9.505

Description

A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities in the form of X509 certificates. The device uses these certificates (called identity certificates) to authenticate itself to various clients communicating with the device using these protocols a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
505
Node name
cpkiMIB
Numeric OID
1.3.6.1.4.1.9.9.505
URN notation
urn:oid:1.3.6.1.4.1.9.9.505
Type
OBJECT IDENTIFIER
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 9 9 505}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) cpkiMIB(505)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) cpkiMIB(505)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/505
  • /ISO/Identified-Organization/6/1/4/1/9/9/505
  • /ISO/3/6/1/4/1/9/9/505
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/cpkiMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/cpkiMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/cpkiMIB
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/cpkiMIB
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/cpkiMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/cpkiMIB
  • Additional combinations skipped.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

cpkiMIB · unspecified

cpkiMIB MODULE-IDENTITY
    LAST-UPDATED        "200510220000Z"
    ORGANIZATION        "Cisco Systems, Inc."
    CONTACT-INFO
        "       Cisco Systems
                Network Management Technology Group

                Postal: 170 W Tasman Drive
                        San Jose, CA  95134
                        USA

                Tel: +1 800 553-NETS

                E-mail:  cs-san@cisco.com"
    DESCRIPTION
        "A networking device may provide several security services
        and  protocols  like SSL, SSH, IPSec/IKE  etc. which  need
        identities  in the form of  X509 certificates. The  device
        uses these  certificates (called identity certificates) to
        authenticate itself to various  clients communicating with
        the device using these protocols and also to provide other
        protection  for  the  communication  like confidentiality,
        integrity and non-repudiation. In addition, the device may
        need to  authenticate the  clients  which involves,  among
        other things, verifying  the certificates presented by the
        clients (peer certificates) during the protocol exchanges.
        The  certificate   verification,  in  turn,  involves  the
        certificate revocation status checking and the certificate
        signature verification. This MIB applies to the public key
        infrastructure (PKI) participation feature which enables a
        networking  device  to  participate in  one  or  more  PKI
        services  (also called  Certificate Authorities)  enabling
        it to  obtain one or more  X509 identity certificates  for
        its own use as well as to verify peer certificates.

        This MIB organizes the various certificates, key-pairs and
        Certificate Authority related information into the tables:
        the trustpoint  table for  certificate and  CA information
        and a key-pair table for the key-pair information for each
        type of key-pair  such as RSA, DSA  etc. An  entry in  the
        trustpoint table corresponds to a trusted CA for obtaining
        an  identity  certificate from and also for  verifying the
        peer certificates  issued by  that CA. The entry  contains
        information   about  the   CA  certificate,  the  identity
        certificate - if obtained - from the CA, the corresponding
        key-pair  from  a key-pair table   (for which the identity
        certificate was obtained) and the  information needed  for
        revocation checking of certitifates issued by  the CA.

        For each type (RSA, DSA etc.) of key-pair supported by the
        device, a key-pair table is present and contains an  entry
        for each key-pair of that type present in the device. This
        allows future expansion of the MIB  to support  additional
        key-pair types (currently only RSA key-pair is supported).

        As seen above, a key-pair entry from a key-pair table  can
        be associated to an entry in the trustpoint table. A  key-
        pair entry can be associated to multiple trustpoint  table
        entries but not vice versa.

        This MIB  supports  the certificate  work-flow operations,
        generally used for generating the key-pairs and  obtaining
        the certificates for them from various CAs. The  following
        are the steps in one typical work-flow:

        1. create a trustpoint  (an entry in  trustpoint table) in
           the device.
        2. Authenticate a CA (this involves manually verifying the
           CA certificate/chain fingerprints and then inputing the
           CA certificate/chain into the trustpoint).
        3. Generate a key-pair (an entry in key-pair table).
        4. Associate the key-pair to the trustpoint.
        5. Generate a pkcs#10 Certificate Signing Request (CSR) in
           the trustpoint.
        7. Submit CSR to the CA and get the identity certificate.
        9. Input the identity certificate into the trustpoint.

        In another typical certificate work-flow, the key-pair and
        the  corresponding  identity certificate are allowed to be
        generated/obtained  outside  the device by  whatever means
        and then input to the device in the pkcs#12 form.

        This MIB does  not support the configuration of individual
        security  services  like SSL, SSH, IPsec/IKE  etc. to  use
        particular trustpoints or  certificates  and key-pairs  in
        them. Instead  the  security  services  certificate  usage
        configuration is supported in the respective feature MIBs.

 
        Glossary of the terms used in this MIB:
         --------------------------------------
        key-pair -
           A pair of public-key cryptographic keys in which one is
           public and the other private.
        RSA key-pair - 
           A key-pair belonging to the RSA public-key cryptography
           algorithm.
        Certificate Authority (CA) -
           A service which issues X509 certificates to certify the
           identity (name) and public-key of end entities.
        X509 -
           A standard for certificates and CRLs.
           Reference: RFC 2459.
        CA certificate - 
           The self-signed certificate of a CA certifying its  own
           identity and public-key.
        CA certificate chain -
           If a CA is certified by another CA which,  in turn, was
           certified by a third CA and so on, ending in a CA which
           is  self-certified,  the  original  CA is  said to be a
           subordinate CA and its CA certificate is a chain  which
           is the set of CA certificates of all CAs involved.
        Identity certificate -
          The certificate of a device issued by a CA in  which the
          device identity and public-key are certified. 
        Trustpoint -
           The various  information  about a CA  (including its CA
           certificate/chain), which the device wants to trust  so
           that it  can use it  to enroll with  the CA to g et  an
           identity certificate and/or  use it to verify the  peer
           certificates issed by the CA.
        Certificate fingerptint -
           The digest of a  certificate computed using MD5 or SHA
           hash algorithm.
        CA authentication -
          The process of configuring  the CA certificate/chain for
          a  trustpoint. The  process  involves   calculating  the
          fingerprints of the CA  certificates  and verifying them
          against the same already published by the CAs.
        Enrollment -
          The process of creating a Certificate Signing Request in
          a trustpoint, submitting it to corresponding CA, getting
          back the identity certificate and  inputing it into  the
          trustpoint.
        Certificate verification -
          The process of verifying the signature on a  certificate
          to see if it was really  signed by the CA who issued it.
          This verification process uses the CA certificate/chain.
          The certificate verification also involves verifying the
          validity of certificate with respect to current  time by
          checking against the  validity  interval  given  in  the
          certificate and the revocation status of the certificate
          as maintained by the CA.
        Certificate Signing Request (CSR) -
          A request to a CA for signing a certificate of an entity.
          The request contains the public key, the name and  other
          attributes of the entity.
        pkcs#10 -
          A standard syntax for the CSR, Reference: RFC 2986.
        pkcs#12 -
          A standard  for  exporting  and  importing a certificate
          along with associated key-pair and CA certificate/chain.
          Reference: PKCS #12 v1.0: Personal Information Exchange
          Syntax Standard, RSA Laboratories, June 24, 1999
        CRL -
          Certificate Revocation List, a list of certificates that
          are revoked, as maintained by a CA.
        OCSP -
          Online Certificate Staus Protocol, a protocol for online
          checking of the revocation status of certificates.
        PEM format -
          A printable text encoding  format for  certificates,
          key-pairs and CRLs, as employed by the Privacy Enhanced
          Mail standard. Reference: RFCs 1421-1424.
         "

    REVISION  "200510220000Z"
    DESCRIPTION
        "Initial version."

    ::= { ciscoMgmt 505 }

cpkiMIB · unspecified

cpkiMIB MODULE-IDENTITY
    LAST-UPDATED        "200510220000Z"
    ORGANIZATION        "Cisco Systems, Inc."
    CONTACT-INFO
        "       Cisco Systems
                Network Management Technology Group

                Postal: 170 W Tasman Drive
                        San Jose, CA  95134
                        USA

                Tel: +1 800 553-NETS

                E-mail:  cs-san@cisco.com"
    DESCRIPTION
        "A networking device may provide several security services
        and  protocols  like SSL, SSH, IPSec/IKE  etc. which  need
        identities  in the form of  X509 certificates. The  device
        uses these  certificates (called identity certificates) to
        authenticate itself to various  clients communicating with
        the device using these protocols and also to provide other
        protection  for  the  communication  like confidentiality,
        integrity and non-repudiation. In addition, the device may
        need to  authenticate the  clients  which involves,  among
        other things, verifying  the certificates presented by the
        clients (peer certificates) during the protocol exchanges.
        The  certificate   verification,  in  turn,  involves  the
        certificate revocation status checking and the certificate
        signature verification. This MIB applies to the public key
        infrastructure (PKI) participation feature which enables a
        networking  device  to  participate in  one  or  more  PKI
        services  (also called  Certificate Authorities)  enabling
        it to  obtain one or more  X509 identity certificates  for
        its own use as well as to verify peer certificates.

        This MIB organizes the various certificates, key-pairs and
        Certificate Authority related information into the tables:
        the trustpoint  table for  certificate and  CA information
        and a key-pair table for the key-pair information for each
        type of key-pair  such as RSA, DSA  etc. An  entry in  the
        trustpoint table corresponds to a trusted CA for obtaining
        an  identity  certificate from and also for  verifying the
        peer certificates  issued by  that CA. The entry  contains
        information   about  the   CA  certificate,  the  identity
        certificate - if obtained - from the CA, the corresponding
        key-pair  from  a key-pair table   (for which the identity
        certificate was obtained) and the  information needed  for
        revocation checking of certitifates issued by  the CA.

        For each type (RSA, DSA etc.) of key-pair supported by the
        device, a key-pair table is present and contains an  entry
        for each key-pair of that type present in the device. This
        allows future expansion of the MIB  to support  additional
        key-pair types (currently only RSA key-pair is supported).

        As seen above, a key-pair entry from a key-pair table  can
        be associated to an entry in the trustpoint table. A  key-
        pair entry can be associated to multiple trustpoint  table
        entries but not vice versa.

        This MIB  supports  the certificate  work-flow operations,
        generally used for generating the key-pairs and  obtaining
        the certificates for them from various CAs. The  following
        are the steps in one typical work-flow:

        1. create a trustpoint  (an entry in  trustpoint table) in
           the device.
        2. Authenticate a CA (this involves manually verifying the
           CA certificate/chain fingerprints and then inputing the
           CA certificate/chain into the trustpoint).
        3. Generate a key-pair (an entry in key-pair table).
        4. Associate the key-pair to the trustpoint.
        5. Generate a pkcs#10 Certificate Signing Request (CSR) in
           the trustpoint.
        7. Submit CSR to the CA and get the identity certificate.
        9. Input the identity certificate into the trustpoint.

        In another typical certificate work-flow, the key-pair and
        the  corresponding  identity certificate are allowed to be
        generated/obtained  outside  the device by  whatever means
        and then input to the device in the pkcs#12 form.

        This MIB does  not support the configuration of individual
        security  services  like SSL, SSH, IPsec/IKE  etc. to  use
        particular trustpoints or  certificates  and key-pairs  in
        them. Instead  the  security  services  certificate  usage
        configuration is supported in the respective feature MIBs.

 
        Glossary of the terms used in this MIB:
         --------------------------------------
        key-pair -
           A pair of public-key cryptographic keys in which one is
           public and the other private.
        RSA key-pair - 
           A key-pair belonging to the RSA public-key cryptography
           algorithm.
        Certificate Authority (CA) -
           A service which issues X509 certificates to certify the
           identity (name) and public-key of end entities.
        X509 -
           A standard for certificates and CRLs.
           Reference: RFC 2459.
        CA certificate - 
           The self-signed certificate of a CA certifying its  own
           identity and public-key.
        CA certificate chain -
           If a CA is certified by another CA which,  in turn, was
           certified by a third CA and so on, ending in a CA which
           is  self-certified,  the  original  CA is  said to be a
           subordinate CA and its CA certificate is a chain  which
           is the set of CA certificates of all CAs involved.
        Identity certificate -
          The certificate of a device issued by a CA in  which the
          device identity and public-key are certified. 
        Trustpoint -
           The various  information  about a CA  (including its CA
           certificate/chain), which the device wants to trust  so
           that it  can use it  to enroll with  the CA to g et  an
           identity certificate and/or  use it to verify the  peer
           certificates issed by the CA.
        Certificate fingerptint -
           The digest of a  certificate computed using MD5 or SHA
           hash algorithm.
        CA authentication -
          The process of configuring  the CA certificate/chain for
          a  trustpoint. The  process  involves   calculating  the
          fingerprints of the CA  certificates  and verifying them
          against the same already published by the CAs.
        Enrollment -
          The process of creating a Certificate Signing Request in
          a trustpoint, submitting it to corresponding CA, getting
          back the identity certificate and  inputing it into  the
          trustpoint.
        Certificate verification -
          The process of verifying the signature on a  certificate
          to see if it was really  signed by the CA who issued it.
          This verification process uses the CA certificate/chain.
          The certificate verification also involves verifying the
          validity of certificate with respect to current  time by
          checking against the  validity  interval  given  in  the
          certificate and the revocation status of the certificate
          as maintained by the CA.
        Certificate Signing Request (CSR) -
          A request to a CA for signing a certificate of an entity.
          The request contains the public key, the name and  other
          attributes of the entity.
        pkcs#10 -
          A standard syntax for the CSR, Reference: RFC 2986.
        pkcs#12 -
          A standard  for  exporting  and  importing a certificate
          along with associated key-pair and CA certificate/chain.
          Reference: PKCS #12 v1.0: Personal Information Exchange
          Syntax Standard, RSA Laboratories, June 24, 1999
        CRL -
          Certificate Revocation List, a list of certificates that
          are revoked, as maintained by a CA.
        OCSP -
          Online Certificate Staus Protocol, a protocol for online
          checking of the revocation status of certificates.
        PEM format -
          A printable text encoding  format for  certificates,
          key-pairs and CRLs, as employed by the Privacy Enhanced
          Mail standard. Reference: RFCs 1421-1424.
         "

    REVISION  "200510220000Z"
    DESCRIPTION
        "Initial version."

    ::= { ciscoMgmt 505 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

A networking device may provide several security services
and protocols like SSL, SSH, IPSec/IKE etc. which need
identities in the form of X509 certificates. The device
uses these certificates (called identity certificates) to
authenticate itself to various clients communicating with
the device using these protocols and also to provide other
protection for the communication like confidentiality,
integrity and non-repudiation. In addition, the device may
need to authenticate the clients which involves, among
other things, verifying the certificates presented by the
clients (peer certificates) during the protocol exchanges.
The certificate verification, in turn, involves the
certificate revocation status checking and the certificate
signature verification. This MIB applies to the public key
infrastructure (PKI) participation feature which enables a
networking device to participate in one or more PKI
services (also called Certificate Authorities) enabling
it to obtain one or more X509 identity certificates for
its own use as well as to verify peer certificates.

This MIB organizes the various certificates, key-pairs and
Certificate Authority related information into the tables:
the trustpoint table for certificate and CA information
and a key-pair table for the key-pair information for each
type of key-pair such as RSA, DSA etc. An entry in the
trustpoint table corresponds to a trusted CA for obtaining
an identity certificate from and also for verifying the
peer certificates issued by that CA. The entry contains
information about the CA certificate, the identity
certificate - if obtained - from the CA, the corresponding
key-pair from a key-pair table (for which the identity
certificate was obtained) and the information needed for
revocation checking of certitifates issued by the CA.

For each type (RSA, DSA etc.) of key-pair supported by the
device, a key-pair table is present and contains an entry
for each key-pair of that type present in the device. This
allows future expansion of the MIB to support additional
key-pair types (currently only RSA key-pair is supported).

As seen above, a key-pair entry from a key-pair table can
be associated to an entry in the trustpoint table. A key-
pair entry can be associated to multiple trustpoint table
entries but not vice versa.

This MIB supports the certificate work-flow operations,
generally used for generating the key-pairs and obtaining
the certificates for them from various CAs. The following
are the steps in one typical work-flow:

1. create a trustpoint (an entry in trustpoint table) in
the device.
2. Authenticate a CA (this involves manually verifying the
CA certificate/chain fingerprints and then inputing the
CA certificate/chain into the trustpoint).
3. Generate a key-pair (an entry in key-pair table).
4. Associate the key-pair to the trustpoint.
5. Generate a pkcs#10 Certificate Signing Request (CSR) in
the trustpoint.
7. Submit CSR to the CA and get the identity certificate.
9. Input the identity certificate into the trustpoint.

In another typical certificate work-flow, the key-pair and
the corresponding identity certificate are allowed to be
generated/obtained outside the device by whatever means
and then input to the device in the pkcs#12 form.

This MIB does not support the configuration of individual
security services like SSL, SSH, IPsec/IKE etc. to use
particular trustpoints or certificates and key-pairs in
them. Instead the security services certificate usage
configuration is supported in the respective feature MIBs.


Glossary of the terms used in this MIB:

key-pair -
A pair of public-key cryptographic keys in which one is
public and the other private.
RSA key-pair -
A key-pair belonging to the RSA public-key cryptography
algorithm.
Certificate Authority (CA) -
A service which issues X509 certificates to certify the
identity (name) and public-key of end entities.
X509 -
A standard for certificates and CRLs.
Reference: RFC 2459.
CA certificate -
The self-signed certificate of a CA certifying its own
identity and public-key.
CA certificate chain -
If a CA is certified by another CA which, in turn, was
certified by a third CA and so on, ending in a CA which
is self-certified, the original CA is said to be a
subordinate CA and its CA certificate is a chain which
is the set of CA certificates of all CAs involved.
Identity certificate -
The certificate of a device issued by a CA in which the
device identity and public-key are certified.
Trustpoint -
The various information about a CA (including its CA
certificate/chain), which the device wants to trust so
that it can use it to enroll with the CA to g et an
identity certificate and/or use it to verify the peer
certificates issed by the CA.
Certificate fingerptint -
The digest of a certificate computed using MD5 or SHA
hash algorithm.
CA authentication -
The process of configuring the CA certificate/chain for
a trustpoint. The process involves calculating the
fingerprints of the CA certificates and verifying them
against the same already published by the CAs.
Enrollment -
The process of creating a Certificate Signing Request in
a trustpoint, submitting it to corresponding CA, getting
back the identity certificate and inputing it into the
trustpoint.
Certificate verification -
The process of verifying the signature on a certificate
to see if it was really signed by the CA who issued it.
This verification process uses the CA certificate/chain.
The certificate verification also involves verifying the
validity of certificate with respect to current time by
checking against the validity interval given in the
certificate and the revocation status of the certificate
as maintained by the CA.
Certificate Signing Request (CSR) -
A request to a CA for signing a certificate of an entity.
The request contains the public key, the name and other
attributes of the entity.
pkcs#10 -
A standard syntax for the CSR, Reference: RFC 2986.
pkcs#12 -
A standard for exporting and importing a certificate
along with associated key-pair and CA certificate/chain.
Reference: PKCS #12 v1.0: Personal Information Exchange
Syntax Standard, RSA Laboratories, June 24, 1999
CRL -
Certificate Revocation List, a list of certificates that
are revoked, as maintained by a CA.
OCSP -
Online Certificate Staus Protocol, a protocol for online
checking of the revocation status of certificates.
PEM format -
A printable text encoding format for certificates,
key-pairs and CRLs, as employed by the Privacy Enhanced
Mail standard. Reference: RFCs 1421-1424.
Sources for this description

Circitor

Parsed from CISCO-PKI-PARTICIPATION-MIB.mib · CISCO-PKI-PARTICIPATION-MIB

Cisco

MIBdepot

Description 2

A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities in the form of X509 certificates. The device uses these certificates (called identity certificates) to authenticate itself to various clients communicating with the device using these protocols and also to provide other protection for the communication like confidentiality, integrity and non-repudiation. In addition, the device may need to authenticate the clients which involves, among other things, verifying the certificates presented by the clients (peer certificates) during the protocol exchanges. The certificate verification, in turn, involves the certificate revocation status checking and the certificate signature verification. This MIB applies to the public key infrastructure (PKI) participation feature which enables a networking device to participate in one or more PKI services (also called Certificate Authorities) enabling it to obtain one or more X509 identity certificates for its own use as well as to verify peer certificates. This MIB organizes the various certificates, key-pairs and Certificate Authority related information into the tables: the trustpoint table for certificate and CA information and a key-pair table for the key-pair information for each type of key-pair such as RSA, DSA etc. An entry in the trustpoint table corresponds to a trusted CA for obtaining an identity certificate from and also for verifying the peer certificates issued by that CA. The entry contains information about the CA certificate, the identity certificate - if obtained - from the CA, the corresponding key-pair from a key-pair table (for which the identity certificate was obtained) and the information needed for revocation checking of certitifates issued by the CA. For each type (RSA, DSA etc.) of key-pair supported by the device, a key-pair table is present and contains an entry for each key-pair of that type present in the device. This allows future expansion of the MIB to support additional key-pair types (currently only RSA key-pair is supported). As seen above, a key-pair entry from a key-pair table can be associated to an entry in the trustpoint table. A key- pair entry can be associated to multiple trustpoint table entries but not vice versa. This MIB supports the certificate work-flow operations, generally used for generating the key-pairs and obtaining the certificates for them from various CAs. The following are the steps in one typical work-flow: 1. create a trustpoint (an entry in trustpoint table) in the device. 2. Authenticate a CA (this involves manually verifying the CA certificate/chain fingerprints and then inputing the CA certificate/chain into the trustpoint). 3. Generate a key-pair (an entry in key-pair table). 4. Associate the key-pair to the trustpoint. 5. Generate a pkcs#10 Certificate Signing Request (CSR) in the trustpoint. 7. Submit CSR to the CA and get the identity certificate. 9. Input the identity certificate into the trustpoint. In another typical certificate work-flow, the key-pair and the corresponding identity certificate are allowed to be generated/obtained outside the device by whatever means and then input to the device in the pkcs#12 form. This MIB does not support the configuration of individual security services like SSL, SSH, IPsec/IKE etc. to use particular trustpoints or certificates and key-pairs in them. Instead the security services certificate usage configuration is supported in the respective feature MIBs. Glossary of the terms used in this MIB: -------------------------------------- key-pair - A pair of public-key cryptographic keys in which one is public and the other private. RSA key-pair - A key-pair belonging to the RSA public-key cryptography algorithm. Certificate Authority (CA) - A service which issues X509 certificates to certify the identity (name) and public-key of end entities. X509 - A standard for certificates and CRLs. Reference: RFC 2459. CA certificate - The self-signed certificate of a CA certifying its own identity and public-key. CA certificate chain - If a CA is certified by another CA which, in turn, was certified by a third CA and so on, ending in a CA which is self-certified, the original CA is said to be a subordinate CA and its CA certificate is a chain which is the set of CA certificates of all CAs involved. Identity certificate - The certificate of a device issued by a CA in which the device identity and public-key are certified. Trustpoint - The various information about a CA (including its CA certificate/chain), which the device wants to trust so that it can use it to enroll with the CA to g et an identity certificate and/or use it to verify the peer certificates issed by the CA. Certificate fingerptint - The digest of a certificate computed using MD5 or SHA hash algorithm. CA authentication - The process of configuring the CA certificate/chain for a trustpoint. The process involves calculating the fingerprints of the CA certificates and verifying them against the same already published by the CAs. Enrollment - The process of creating a Certificate Signing Request in a trustpoint, submitting it to corresponding CA, getting back the identity certificate and inputing it into the trustpoint. Certificate verification - The process of verifying the signature on a certificate to see if it was really signed by the CA who issued it. This verification process uses the CA certificate/chain. The certificate verification also involves verifying the validity of certificate with respect to current time by checking against the validity interval given in the certificate and the revocation status of the certificate as maintained by the CA. Certificate Signing Request (CSR) - A request to a CA for signing a certificate of an entity. The request contains the public key, the name and other attributes of the entity. pkcs#10 - A standard syntax for the CSR, Reference: RFC 2986. pkcs#12 - A standard for exporting and importing a certificate along with associated key-pair and CA certificate/chain. Reference: PKCS #12 v1.0: Personal Information Exchange Syntax Standard, RSA Laboratories, June 24, 1999 CRL - Certificate Revocation List, a list of certificates that are revoked, as maintained by a CA. OCSP - Online Certificate Staus Protocol, a protocol for online checking of the revocation status of certificates. PEM format - A printable text encoding format for certificates, key-pairs and CRLs, as employed by the Privacy Enhanced Mail standard. Reference: RFCs 1421-1424.

Sources for this description

CircitorCiscoCisco MIB copies (LibreNMS/Observium Community)MIBdepotNetdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 2Circitor, Cisco, and others1 record · 5 sources

Description 2

cpkiMIB · unspecifiedCircitor, Cisco, and others5 sources

Status in source: unspecified.

Names: cpkiMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "cpkiMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303531303232303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems, Inc.\"",
    "CONTACT-INFO",
    "\" Cisco Systems Network Management Technology Group Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-san@cisco.com\"",
    "DESCRIPTION",
    "\"A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities in the form of X509 certificates. The device uses these certificates (called identity certificates) to authenticate itself to various clients communicating with the device using these protocols and also to provide other protection for the communication like confidentiality, integrity and non-repudiation. In addition, the device may need to authenticate the clients which involves, among other things, verifying the certificates presented by the clients (peer certificates) during the protocol exchanges. The certificate verification, in turn, involves the certificate revocation status checking and the certificate signature verification. This MIB applies to the public key infrastructure (PKI) participation feature which enables a networking device to participate in one or more PKI services (also called Certificate Authorities) enabling it to obtain one or more X509 identity certificates for its own use as well as to verify peer certificates. This MIB organizes the various certificates, key-pairs and Certificate Authority related information into the tables: the trustpoint table for certificate and CA information and a key-pair table for the key-pair information for each type of key-pair such as RSA, DSA etc. An entry in the trustpoint table corresponds to a trusted CA for obtaining an identity certificate from and also for verifying the peer certificates issued by that CA. The entry contains information about the CA certificate, the identity certificate - if obtained - from the CA, the corresponding key-pair from a key-pair table (for which the identity certificate was obtained) and the information needed for revocation checking of certitifates issued by the CA. For each type (RSA, DSA etc.) of key-pair supported by the device, a key-pair table is present and contains an entry for each key-pair of that type present in the device. This allows future expansion of the MIB to support additional key-pair types (currently only RSA key-pair is supported). As seen above, a key-pair entry from a key-pair table can be associated to an entry in the trustpoint table. A key- pair entry can be associated to multiple trustpoint table entries but not vice versa. This MIB supports the certificate work-flow operations, generally used for generating the key-pairs and obtaining the certificates for them from various CAs. The following are the steps in one typical work-flow: 1. create a trustpoint (an entry in trustpoint table) in the device. 2. Authenticate a CA (this involves manually verifying the CA certificate/chain fingerprints and then inputing the CA certificate/chain into the trustpoint). 3. Generate a key-pair (an entry in key-pair table). 4. Associate the key-pair to the trustpoint. 5. Generate a pkcs#10 Certificate Signing Request (CSR) in the trustpoint. 7. Submit CSR to the CA and get the identity certificate. 9. Input the identity certificate into the trustpoint. In another typical certificate work-flow, the key-pair and the corresponding identity certificate are allowed to be generated/obtained outside the device by whatever means and then input to the device in the pkcs#12 form. This MIB does not support the configuration of individual security services like SSL, SSH, IPsec/IKE etc. to use particular trustpoints or certificates and key-pairs in them. Instead the security services certificate usage configuration is supported in the respective feature MIBs. Glossary of the terms used in this MIB: -------------------------------------- key-pair - A pair of public-key cryptographic keys in which one is public and the other private. RSA key-pair - A key-pair belonging to the RSA public-key cryptography algorithm. Certificate Authority (CA) - A service which issues X509 certificates to certify the identity (name) and public-key of end entities. X509 - A standard for certificates and CRLs. Reference: RFC 2459. CA certificate - The self-signed certificate of a CA certifying its own identity and public-key. CA certificate chain - If a CA is certified by another CA which, in turn, was certified by a third CA and so on, ending in a CA which is self-certified, the original CA is said to be a subordinate CA and its CA certificate is a chain which is the set of CA certificates of all CAs involved. Identity certificate - The certificate of a device issued by a CA in which the device identity and public-key are certified. Trustpoint - The various information about a CA (including its CA certificate/chain), which the device wants to trust so that it can use it to enroll with the CA to g et an identity certificate and/or use it to verify the peer certificates issed by the CA. Certificate fingerptint - The digest of a certificate computed using MD5 or SHA hash algorithm. CA authentication - The process of configuring the CA certificate/chain for a trustpoint. The process involves calculating the fingerprints of the CA certificates and verifying them against the same already published by the CAs. Enrollment - The process of creating a Certificate Signing Request in a trustpoint, submitting it to corresponding CA, getting back the identity certificate and inputing it into the trustpoint. Certificate verification - The process of verifying the signature on a certificate to see if it was really signed by the CA who issued it. This verification process uses the CA certificate/chain. The certificate verification also involves verifying the validity of certificate with respect to current time by checking against the validity interval given in the certificate and the revocation status of the certificate as maintained by the CA. Certificate Signing Request (CSR) - A request to a CA for signing a certificate of an entity. The request contains the public key, the name and other attributes of the entity. pkcs#10 - A standard syntax for the CSR, Reference: RFC 2986. pkcs#12 - A standard for exporting and importing a certificate along with associated key-pair and CA certificate/chain. Reference: PKCS #12 v1.0: Personal Information Exchange Syntax Standard, RSA Laboratories, June 24, 1999 CRL - Certificate Revocation List, a list of certificates that are revoked, as maintained by a CA. OCSP - Online Certificate Staus Protocol, a protocol for online checking of the revocation status of certificates. PEM format - A printable text encoding format for certificates, key-pairs and CRLs, as employed by the Privacy Enhanced Mail standard. Reference: RFCs 1421-1424. \"",
    "REVISION",
    [
      "literal",
      "223230303531303232303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "505",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200510220000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems, Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems Network Management Technology Group Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-san@cisco.com"
    ],
    [
      "DESCRIPTION",
      "A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities in the form of X509 certificates. The device uses these certificates (called identity certificates) to authenticate itself to various clients communicating with the device using these protocols and also to provide other protection for the communication like confidentiality, integrity and non-repudiation. In addition, the device may need to authenticate the clients which involves, among other things, verifying the certificates presented by the clients (peer certificates) during the protocol exchanges. The certificate verification, in turn, involves the certificate revocation status checking and the certificate signature verification. This MIB applies to the public key infrastructure (PKI) participation feature which enables a networking device to participate in one or more PKI services (also called Certificate Authorities) enabling it to obtain one or more X509 identity certificates for its own use as well as to verify peer certificates. This MIB organizes the various certificates, key-pairs and Certificate Authority related information into the tables: the trustpoint table for certificate and CA information and a key-pair table for the key-pair information for each type of key-pair such as RSA, DSA etc. An entry in the trustpoint table corresponds to a trusted CA for obtaining an identity certificate from and also for verifying the peer certificates issued by that CA. The entry contains information about the CA certificate, the identity certificate - if obtained - from the CA, the corresponding key-pair from a key-pair table (for which the identity certificate was obtained) and the information needed for revocation checking of certitifates issued by the CA. For each type (RSA, DSA etc.) of key-pair supported by the device, a key-pair table is present and contains an entry for each key-pair of that type present in the device. This allows future expansion of the MIB to support additional key-pair types (currently only RSA key-pair is supported). As seen above, a key-pair entry from a key-pair table can be associated to an entry in the trustpoint table. A key- pair entry can be associated to multiple trustpoint table entries but not vice versa. This MIB supports the certificate work-flow operations, generally used for generating the key-pairs and obtaining the certificates for them from various CAs. The following are the steps in one typical work-flow: 1. create a trustpoint (an entry in trustpoint table) in the device. 2. Authenticate a CA (this involves manually verifying the CA certificate/chain fingerprints and then inputing the CA certificate/chain into the trustpoint). 3. Generate a key-pair (an entry in key-pair table). 4. Associate the key-pair to the trustpoint. 5. Generate a pkcs#10 Certificate Signing Request (CSR) in the trustpoint. 7. Submit CSR to the CA and get the identity certificate. 9. Input the identity certificate into the trustpoint. In another typical certificate work-flow, the key-pair and the corresponding identity certificate are allowed to be generated/obtained outside the device by whatever means and then input to the device in the pkcs#12 form. This MIB does not support the configuration of individual security services like SSL, SSH, IPsec/IKE etc. to use particular trustpoints or certificates and key-pairs in them. Instead the security services certificate usage configuration is supported in the respective feature MIBs. Glossary of the terms used in this MIB: -------------------------------------- key-pair - A pair of public-key cryptographic keys in which one is public and the other private. RSA key-pair - A key-pair belonging to the RSA public-key cryptography algorithm. Certificate Authority (CA) - A service which issues X509 certificates to certify the identity (name) and public-key of end entities. X509 - A standard for certificates and CRLs. Reference: RFC 2459. CA certificate - The self-signed certificate of a CA certifying its own identity and public-key. CA certificate chain - If a CA is certified by another CA which, in turn, was certified by a third CA and so on, ending in a CA which is self-certified, the original CA is said to be a subordinate CA and its CA certificate is a chain which is the set of CA certificates of all CAs involved. Identity certificate - The certificate of a device issued by a CA in which the device identity and public-key are certified. Trustpoint - The various information about a CA (including its CA certificate/chain), which the device wants to trust so that it can use it to enroll with the CA to g et an identity certificate and/or use it to verify the peer certificates issed by the CA. Certificate fingerptint - The digest of a certificate computed using MD5 or SHA hash algorithm. CA authentication - The process of configuring the CA certificate/chain for a trustpoint. The process involves calculating the fingerprints of the CA certificates and verifying them against the same already published by the CAs. Enrollment - The process of creating a Certificate Signing Request in a trustpoint, submitting it to corresponding CA, getting back the identity certificate and inputing it into the trustpoint. Certificate verification - The process of verifying the signature on a certificate to see if it was really signed by the CA who issued it. This verification process uses the CA certificate/chain. The certificate verification also involves verifying the validity of certificate with respect to current time by checking against the validity interval given in the certificate and the revocation status of the certificate as maintained by the CA. Certificate Signing Request (CSR) - A request to a CA for signing a certificate of an entity. The request contains the public key, the name and other attributes of the entity. pkcs#10 - A standard syntax for the CSR, Reference: RFC 2986. pkcs#12 - A standard for exporting and importing a certificate along with associated key-pair and CA certificate/chain. Reference: PKCS #12 v1.0: Personal Information Exchange Syntax Standard, RSA Laboratories, June 24, 1999 CRL - Certificate Revocation List, a list of certificates that are revoked, as maintained by a CA. OCSP - Online Certificate Staus Protocol, a protocol for online checking of the revocation status of certificates. PEM format - A printable text encoding format for certificates, key-pairs and CRLs, as employed by the Privacy Enhanced Mail standard. Reference: RFCs 1421-1424."
    ],
    [
      "Revisions",
      [
        [
          "200510220000Z",
          [
            "DESCRIPTION",
            "Initial version."
          ]
        ]
      ]
    ]
  ]
}

Historical records

Additional source information

Information from Circitor
cpkiMIB MODULE-IDENTITY
    LAST-UPDATED        "200510220000Z"
    ORGANIZATION        "Cisco Systems, Inc."
    CONTACT-INFO
        "       Cisco Systems
                Network Management Technology Group

                Postal: 170 W Tasman Drive
                        San Jose, CA  95134
                        USA

                Tel: +1 800 553-NETS

                E-mail:  cs-san@cisco.com"
    DESCRIPTION
        "A networking device may provide several security services
        and  protocols  like SSL, SSH, IPSec/IKE  etc. which  need
        identities  in the form of  X509 certificates. The  device
        uses these  certificates (called identity certificates) to
        authenticate itself to various  clients communicating with
        the device using these protocols and also to provide other
        protection  for  the  communication  like confidentiality,
        integrity and non-repudiation. In addition, the device may
        need to  authenticate the  clients  which involves,  among
        other things, verifying  the certificates presented by the
        clients (peer certificates) during the protocol exchanges.
        The  certificate   verification,  in  turn,  involves  the
        certificate revocation status checking and the certificate
        signature verification. This MIB applies to the public key
        infrastructure (PKI) participation feature which enables a
        networking  device  to  participate in  one  or  more  PKI
        services  (also called  Certificate Authorities)  enabling
        it to  obtain one or more  X509 identity certificates  for
        its own use as well as to verify peer certificates.

        This MIB organizes the various certificates, key-pairs and
        Certificate Authority related information into the tables:
        the trustpoint  table for  certificate and  CA information
        and a key-pair table for the key-pair information for each
        type of key-pair  such as RSA, DSA  etc. An  entry in  the
        trustpoint table corresponds to a trusted CA for obtaining
        an  identity  certificate from and also for  verifying the
        peer certificates  issued by  that CA. The entry  contains
        information   about  the   CA  certificate,  the  identity
        certificate - if obtained - from the CA, the corresponding
        key-pair  from  a key-pair table   (for which the identity
        certificate was obtained) and the  information needed  for
        revocation checking of certitifates issued by  the CA.

        For each type (RSA, DSA etc.) of key-pair supported by the
        device, a key-pair table is present and contains an  entry
        for each key-pair of that type present in the device. This
        allows future expansion of the MIB  to support  additional
        key-pair types (currently only RSA key-pair is supported).

        As seen above, a key-pair entry from a key-pair table  can
        be associated to an entry in the trustpoint table. A  key-
        pair entry can be associated to multiple trustpoint  table
        entries but not vice versa.

        This MIB  supports  the certificate  work-flow operations,
        generally used for generating the key-pairs and  obtaining
        the certificates for them from various CAs. The  following
        are the steps in one typical work-flow:

        1. create a trustpoint  (an entry in  trustpoint table) in
           the device.
        2. Authenticate a CA (this involves manually verifying the
           CA certificate/chain fingerprints and then inputing the
           CA certificate/chain into the trustpoint).
        3. Generate a key-pair (an entry in key-pair table).
        4. Associate the key-pair to the trustpoint.
        5. Generate a pkcs#10 Certificate Signing Request (CSR) in
           the trustpoint.
        7. Submit CSR to the CA and get the identity certificate.
        9. Input the identity certificate into the trustpoint.

        In another typical certificate work-flow, the key-pair and
        the  corresponding  identity certificate are allowed to be
        generated/obtained  outside  the device by  whatever means
        and then input to the device in the pkcs#12 form.

        This MIB does  not support the configuration of individual
        security  services  like SSL, SSH, IPsec/IKE  etc. to  use
        particular trustpoints or  certificates  and key-pairs  in
        them. Instead  the  security  services  certificate  usage
        configuration is supported in the respective feature MIBs.

 
        Glossary of the terms used in this MIB:
         
        key-pair -
           A pair of public-key cryptographic keys in which one is
           public and the other private.
        RSA key-pair - 
           A key-pair belonging to the RSA public-key cryptography
           algorithm.
        Certificate Authority (CA) -
           A service which issues X509 certificates to certify the
           identity (name) and public-key of end entities.
        X509 -
           A standard for certificates and CRLs.
           Reference: RFC 2459.
        CA certificate - 
           The self-signed certificate of a CA certifying its  own
           identity and public-key.
        CA certificate chain -
           If a CA is certified by another CA which,  in turn, was
           certified by a third CA and so on, ending in a CA which
           is  self-certified,  the  original  CA is  said to be a
           subordinate CA and its CA certificate is a chain  which
           is the set of CA certificates of all CAs involved.
        Identity certificate -
          The certificate of a device issued by a CA in  which the
          device identity and public-key are certified. 
        Trustpoint -
           The various  information  about a CA  (including its CA
           certificate/chain), which the device wants to trust  so
           that it  can use it  to enroll with  the CA to g et  an
           identity certificate and/or  use it to verify the  peer
           certificates issed by the CA.
        Certificate fingerptint -
           The digest of a  certificate computed using MD5 or SHA
           hash algorithm.
        CA authentication -
          The process of configuring  the CA certificate/chain for
          a  trustpoint. The  process  involves   calculating  the
          fingerprints of the CA  certificates  and verifying them
          against the same already published by the CAs.
        Enrollment -
          The process of creating a Certificate Signing Request in
          a trustpoint, submitting it to corresponding CA, getting
          back the identity certificate and  inputing it into  the
          trustpoint.
        Certificate verification -
          The process of verifying the signature on a  certificate
          to see if it was really  signed by the CA who issued it.
          This verification process uses the CA certificate/chain.
          The certificate verification also involves verifying the
          validity of certificate with respect to current  time by
          checking against the  validity  interval  given  in  the
          certificate and the revocation status of the certificate
          as maintained by the CA.
        Certificate Signing Request (CSR) -
          A request to a CA for signing a certificate of an entity.
          The request contains the public key, the name and  other
          attributes of the entity.
        pkcs#10 -
          A standard syntax for the CSR, Reference: RFC 2986.
        pkcs#12 -
          A standard  for  exporting  and  importing a certificate
          along with associated key-pair and CA certificate/chain.
          Reference: PKCS #12 v1.0: Personal Information Exchange
          Syntax Standard, RSA Laboratories, June 24, 1999
        CRL -
          Certificate Revocation List, a list of certificates that
          are revoked, as maintained by a CA.
        OCSP -
          Online Certificate Staus Protocol, a protocol for online
          checking of the revocation status of certificates.
        PEM format -
          A printable text encoding  format for  certificates,
          key-pairs and CRLs, as employed by the Privacy Enhanced
          Mail standard. Reference: RFCs 1421-1424.
         "

    REVISION  "200510220000Z"
    DESCRIPTION
        "Initial version."

    ::= { ciscoMgmt 505 }
Information from Cisco SMIv1

Source file: Download CISCO-PKI-PARTICIPATION-MIB-V1SMI.my · Publisher's file

Source file: Download CISCO-PKI-PARTICIPATION-MIB-V1SMI.my.txt

cpkiMIB OBJECT IDENTIFIER ::= { ciscoMgmt 505 }
Information from OID Repository
Vendor: Cisco
Module: CISCO-PKI-PARTICIPATION-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot
cpkiMIB MODULE-IDENTITY
    LAST-UPDATED        "200510220000Z"
    ORGANIZATION        "Cisco Systems, Inc."
    CONTACT-INFO
        "       Cisco Systems
                Network Management Technology Group

                Postal: 170 W Tasman Drive
                        San Jose, CA  95134
                        USA

                Tel: +1 800 553-NETS

                E-mail:  cs-san@cisco.com"
    DESCRIPTION
        "A networking device may provide several security services
        and  protocols  like SSL, SSH, IPSec/IKE  etc. which  need
        identities  in the form of  X509 certificates. The  device
        uses these  certificates (called identity certificates) to
        authenticate itself to various  clients communicating with
        the device using these protocols and also to provide other
        protection  for  the  communication  like confidentiality,
        integrity and non-repudiation. In addition, the device may
        need to  authenticate the  clients  which involves,  among
        other things, verifying  the certificates presented by the
        clients (peer certificates) during the protocol exchanges.
        The  certificate   verification,  in  turn,  involves  the
        certificate revocation status checking and the certificate
        signature verification. This MIB applies to the public key
        infrastructure (PKI) participation feature which enables a
        networking  device  to  participate in  one  or  more  PKI
        services  (also called  Certificate Authorities)  enabling
        it to  obtain one or more  X509 identity certificates  for
        its own use as well as to verify peer certificates.

        This MIB organizes the various certificates, key-pairs and
        Certificate Authority related information into the tables:
        the trustpoint  table for  certificate and  CA information
        and a key-pair table for the key-pair information for each
        type of key-pair  such as RSA, DSA  etc. An  entry in  the
        trustpoint table corresponds to a trusted CA for obtaining
        an  identity  certificate from and also for  verifying the
        peer certificates  issued by  that CA. The entry  contains
        information   about  the   CA  certificate,  the  identity
        certificate - if obtained - from the CA, the corresponding
        key-pair  from  a key-pair table   (for which the identity
        certificate was obtained) and the  information needed  for
        revocation checking of certitifates issued by  the CA.

        For each type (RSA, DSA etc.) of key-pair supported by the
        device, a key-pair table is present and contains an  entry
        for each key-pair of that type present in the device. This
        allows future expansion of the MIB  to support  additional
        key-pair types (currently only RSA key-pair is supported).

        As seen above, a key-pair entry from a key-pair table  can
        be associated to an entry in the trustpoint table. A  key-
        pair entry can be associated to multiple trustpoint  table
        entries but not vice versa.

        This MIB  supports  the certificate  work-flow operations,
        generally used for generating the key-pairs and  obtaining
        the certificates for them from various CAs. The  following
        are the steps in one typical work-flow:

        1. create a trustpoint  (an entry in  trustpoint table) in
           the device.
        2. Authenticate a CA (this involves manually verifying the
           CA certificate/chain fingerprints and then inputing the
           CA certificate/chain into the trustpoint).
        3. Generate a key-pair (an entry in key-pair table).
        4. Associate the key-pair to the trustpoint.
        5. Generate a pkcs#10 Certificate Signing Request (CSR) in
           the trustpoint.
        7. Submit CSR to the CA and get the identity certificate.
        9. Input the identity certificate into the trustpoint.

        In another typical certificate work-flow, the key-pair and
        the  corresponding  identity certificate are allowed to be
        generated/obtained  outside  the device by  whatever means
        and then input to the device in the pkcs#12 form.

        This MIB does  not support the configuration of individual
        security  services  like SSL, SSH, IPsec/IKE  etc. to  use
        particular trustpoints or  certificates  and key-pairs  in
        them. Instead  the  security  services  certificate  usage
        configuration is supported in the respective feature MIBs.

 
        Glossary of the terms used in this MIB:
         
        key-pair -
           A pair of public-key cryptographic keys in which one is
           public and the other private.
        RSA key-pair - 
           A key-pair belonging to the RSA public-key cryptography
           algorithm.
        Certificate Authority (CA) -
           A service which issues X509 certificates to certify the
           identity (name) and public-key of end entities.
        X509 -
           A standard for certificates and CRLs.
           Reference: RFC 2459.
        CA certificate - 
           The self-signed certificate of a CA certifying its  own
           identity and public-key.
        CA certificate chain -
           If a CA is certified by another CA which,  in turn, was
           certified by a third CA and so on, ending in a CA which
           is  self-certified,  the  original  CA is  said to be a
           subordinate CA and its CA certificate is a chain  which
           is the set of CA certificates of all CAs involved.
        Identity certificate -
          The certificate of a device issued by a CA in  which the
          device identity and public-key are certified. 
        Trustpoint -
           The various  information  about a CA  (including its CA
           certificate/chain), which the device wants to trust  so
           that it  can use it  to enroll with  the CA to g et  an
           identity certificate and/or  use it to verify the  peer
           certificates issed by the CA.
        Certificate fingerptint -
           The digest of a  certificate computed using MD5 or SHA
           hash algorithm.
        CA authentication -
          The process of configuring  the CA certificate/chain for
          a  trustpoint. The  process  involves   calculating  the
          fingerprints of the CA  certificates  and verifying them
          against the same already published by the CAs.
        Enrollment -
          The process of creating a Certificate Signing Request in
          a trustpoint, submitting it to corresponding CA, getting
          back the identity certificate and  inputing it into  the
          trustpoint.
        Certificate verification -
          The process of verifying the signature on a  certificate
          to see if it was really  signed by the CA who issued it.
          This verification process uses the CA certificate/chain.
          The certificate verification also involves verifying the
          validity of certificate with respect to current  time by
          checking against the  validity  interval  given  in  the
          certificate and the revocation status of the certificate
          as maintained by the CA.
        Certificate Signing Request (CSR) -
          A request to a CA for signing a certificate of an entity.
          The request contains the public key, the name and  other
          attributes of the entity.
        pkcs#10 -
          A standard syntax for the CSR, Reference: RFC 2986.
        pkcs#12 -
          A standard  for  exporting  and  importing a certificate
          along with associated key-pair and CA certificate/chain.
          Reference: PKCS #12 v1.0: Personal Information Exchange
          Syntax Standard, RSA Laboratories, June 24, 1999
        CRL -
          Certificate Revocation List, a list of certificates that
          are revoked, as maintained by a CA.
        OCSP -
          Online Certificate Staus Protocol, a protocol for online
          checking of the revocation status of certificates.
        PEM format -
          A printable text encoding  format for  certificates,
          key-pairs and CRLs, as employed by the Privacy Enhanced
          Mail standard. Reference: RFCs 1421-1424.
         "

    REVISION  "200510220000Z"
    DESCRIPTION
        "Initial version."

    ::= { ciscoMgmt 505 }
Information from Cisco
cpkiMIB MODULE-IDENTITY
    LAST-UPDATED        "200510220000Z"
    ORGANIZATION        "Cisco Systems, Inc."
    CONTACT-INFO
        "       Cisco Systems
                Network Management Technology Group

                Postal: 170 W Tasman Drive
                        San Jose, CA  95134
                        USA

                Tel: +1 800 553-NETS

                E-mail:  cs-san@cisco.com"
    DESCRIPTION
        "A networking device may provide several security services
        and  protocols  like SSL, SSH, IPSec/IKE  etc. which  need
        identities  in the form of  X509 certificates. The  device
        uses these  certificates (called identity certificates) to
        authenticate itself to various  clients communicating with
        the device using these protocols and also to provide other
        protection  for  the  communication  like confidentiality,
        integrity and non-repudiation. In addition, the device may
        need to  authenticate the  clients  which involves,  among
        other things, verifying  the certificates presented by the
        clients (peer certificates) during the protocol exchanges.
        The  certificate   verification,  in  turn,  involves  the
        certificate revocation status checking and the certificate
        signature verification. This MIB applies to the public key
        infrastructure (PKI) participation feature which enables a
        networking  device  to  participate in  one  or  more  PKI
        services  (also called  Certificate Authorities)  enabling
        it to  obtain one or more  X509 identity certificates  for
        its own use as well as to verify peer certificates.

        This MIB organizes the various certificates, key-pairs and
        Certificate Authority related information into the tables:
        the trustpoint  table for  certificate and  CA information
        and a key-pair table for the key-pair information for each
        type of key-pair  such as RSA, DSA  etc. An  entry in  the
        trustpoint table corresponds to a trusted CA for obtaining
        an  identity  certificate from and also for  verifying the
        peer certificates  issued by  that CA. The entry  contains
        information   about  the   CA  certificate,  the  identity
        certificate - if obtained - from the CA, the corresponding
        key-pair  from  a key-pair table   (for which the identity
        certificate was obtained) and the  information needed  for
        revocation checking of certitifates issued by  the CA.

        For each type (RSA, DSA etc.) of key-pair supported by the
        device, a key-pair table is present and contains an  entry
        for each key-pair of that type present in the device. This
        allows future expansion of the MIB  to support  additional
        key-pair types (currently only RSA key-pair is supported).

        As seen above, a key-pair entry from a key-pair table  can
        be associated to an entry in the trustpoint table. A  key-
        pair entry can be associated to multiple trustpoint  table
        entries but not vice versa.

        This MIB  supports  the certificate  work-flow operations,
        generally used for generating the key-pairs and  obtaining
        the certificates for them from various CAs. The  following
        are the steps in one typical work-flow:

        1. create a trustpoint  (an entry in  trustpoint table) in
           the device.
        2. Authenticate a CA (this involves manually verifying the
           CA certificate/chain fingerprints and then inputing the
           CA certificate/chain into the trustpoint).
        3. Generate a key-pair (an entry in key-pair table).
        4. Associate the key-pair to the trustpoint.
        5. Generate a pkcs#10 Certificate Signing Request (CSR) in
           the trustpoint.
        7. Submit CSR to the CA and get the identity certificate.
        9. Input the identity certificate into the trustpoint.

        In another typical certificate work-flow, the key-pair and
        the  corresponding  identity certificate are allowed to be
        generated/obtained  outside  the device by  whatever means
        and then input to the device in the pkcs#12 form.

        This MIB does  not support the configuration of individual
        security  services  like SSL, SSH, IPsec/IKE  etc. to  use
        particular trustpoints or  certificates  and key-pairs  in
        them. Instead  the  security  services  certificate  usage
        configuration is supported in the respective feature MIBs.

 
        Glossary of the terms used in this MIB:
         
        key-pair -
           A pair of public-key cryptographic keys in which one is
           public and the other private.
        RSA key-pair - 
           A key-pair belonging to the RSA public-key cryptography
           algorithm.
        Certificate Authority (CA) -
           A service which issues X509 certificates to certify the
           identity (name) and public-key of end entities.
        X509 -
           A standard for certificates and CRLs.
           Reference: RFC 2459.
        CA certificate - 
           The self-signed certificate of a CA certifying its  own
           identity and public-key.
        CA certificate chain -
           If a CA is certified by another CA which,  in turn, was
           certified by a third CA and so on, ending in a CA which
           is  self-certified,  the  original  CA is  said to be a
           subordinate CA and its CA certificate is a chain  which
           is the set of CA certificates of all CAs involved.
        Identity certificate -
          The certificate of a device issued by a CA in  which the
          device identity and public-key are certified. 
        Trustpoint -
           The various  information  about a CA  (including its CA
           certificate/chain), which the device wants to trust  so
           that it  can use it  to enroll with  the CA to g et  an
           identity certificate and/or  use it to verify the  peer
           certificates issed by the CA.
        Certificate fingerptint -
           The digest of a  certificate computed using MD5 or SHA
           hash algorithm.
        CA authentication -
          The process of configuring  the CA certificate/chain for
          a  trustpoint. The  process  involves   calculating  the
          fingerprints of the CA  certificates  and verifying them
          against the same already published by the CAs.
        Enrollment -
          The process of creating a Certificate Signing Request in
          a trustpoint, submitting it to corresponding CA, getting
          back the identity certificate and  inputing it into  the
          trustpoint.
        Certificate verification -
          The process of verifying the signature on a  certificate
          to see if it was really  signed by the CA who issued it.
          This verification process uses the CA certificate/chain.
          The certificate verification also involves verifying the
          validity of certificate with respect to current  time by
          checking against the  validity  interval  given  in  the
          certificate and the revocation status of the certificate
          as maintained by the CA.
        Certificate Signing Request (CSR) -
          A request to a CA for signing a certificate of an entity.
          The request contains the public key, the name and  other
          attributes of the entity.
        pkcs#10 -
          A standard syntax for the CSR, Reference: RFC 2986.
        pkcs#12 -
          A standard  for  exporting  and  importing a certificate
          along with associated key-pair and CA certificate/chain.
          Reference: PKCS #12 v1.0: Personal Information Exchange
          Syntax Standard, RSA Laboratories, June 24, 1999
        CRL -
          Certificate Revocation List, a list of certificates that
          are revoked, as maintained by a CA.
        OCSP -
          Online Certificate Staus Protocol, a protocol for online
          checking of the revocation status of certificates.
        PEM format -
          A printable text encoding  format for  certificates,
          key-pairs and CRLs, as employed by the Privacy Enhanced
          Mail standard. Reference: RFCs 1421-1424.
         "

    REVISION  "200510220000Z"
    DESCRIPTION
        "Initial version."

    ::= { ciscoMgmt 505 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.505.0 cpkiMIBNotifs00
1.3.6.1.4.1.9.9.505.1 cpkiMIBObjects137
1.3.6.1.4.1.9.9.505.2 cpkiMIBConform24

Siblings (706)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.443 ciscoCommonMgmtMIB337 MIB module for integrating different elements of
managing a device. For example, different device access
methods like SNMP, CLI, …
1.3.6.1.4.1.9.9.445 ciscoQinqVlanMIB325 This MIB defines configuration and monitoring capabilities
relating to 802.1QinQ interfaces. QinQ interfaces are capable
of term…
1.3.6.1.4.1.9.9.447 ciscoScsiFlowMIB399 A SCSI Flow is described as a SCSI Initiator
SCSI Target combination. This MIB is used to
configure and monitor SCSI Flows.

Gloss…
1.3.6.1.4.1.9.9.448 ciscoSsmProvMIB226 This MIB is used to provision features
on a Data Path Processor (DPP) of a Storage Service
Module (SSM). A DPP is assigned to a c…
1.3.6.1.4.1.9.9.449 ciscoEigrpMIB3110 Enhanced Interior Gateway Protocol (EIGRP) is a Cisco
proprietary distance vector routing protocol. It is based on
the Diffusin…
1.3.6.1.4.1.9.9.450 ciscoCableAdmCtrlMIB3123 This MIB module defines the managed objects enabling
the management of Cable Modem Termination System
(CMTS) admission control.

CM…
1.3.6.1.4.1.9.9.451 ciscoIpUrpfMIB347 Unicast Reverse Path Forwarding (URPF) is a function
that checks the validity of the source address of IP
packets received on an …
1.3.6.1.4.1.9.9.454 ciscoDot11LbsMIB323 This MIB module supports network management
for Location Based Services on IEEE 802.11 wireless
LAN devices. Location Based Serv…
1.3.6.1.4.1.9.9.455 ciscoImageTc00 ciscoImageTc MODULE-IDENTITY
LAST-UPDATED "200501120000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Custom…
1.3.6.1.4.1.9.9.456 ciscoDot11WidsMIB350 This MIB is intended to be implemented on the
following IOS based network entities for the purpose
of providing network managemen…
1.3.6.1.4.1.9.9.457 ciscoWdsIdsMIB218 This MIB is intended to be implemented on all
IOS based network entities that provide Wireless
Domain Services, for the purpose o…
1.3.6.1.4.1.9.9.458 ciscoApplianceRedundancyMIB347 This mib defines the SNMP objects to report the status of
High Availability (HA) functionality in Cisco network
management applia…
1.3.6.1.4.1.9.9.459 ciscoBitsClockMIB321 This MIB provides information on Building Integrated
Timing Supply(BITS) clocking sources and modes of
operations. It is used to…
1.3.6.1.4.1.9.9.460 ciscoTpcMIB324 The MIB module for Third Party Copy(TPC):
Third Party Copy derives its name from the fact
that there are three entities involved …
1.3.6.1.4.1.9.9.461 ciscoEtherCfmMIB339 This MIB module defines the managed objects
and notifications for Ethernet Connectivity
Fault Management (CFM).

CFM is an end-to-e…
1.3.6.1.4.1.9.9.463 ciscoSanTapMIB330 MIB module to provide information about the SanTap
service configuration.

SanTap is a fibre channel switch based capability that
p…
1.3.6.1.4.1.9.9.466 ciscoEthernetAccessMIB220 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
an edge dev…
1.3.6.1.4.1.9.9.467 ciscoCryptoAcceleratorMIB3107 The MIB module for monitoring the identity, status,
activity and faults of crypto accelerator (CA) modules
used in devices implem…
1.3.6.1.4.1.9.9.468 ciscoContextMappingMIB235 A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple…
1.3.6.1.4.1.9.9.470 ciscoEnhancedSlbMIB3106 The MIB for managing Server Load Balancing
Manager(s), and products supporting Server
Load Balancing(SLB) features.

This MIB exten…
1.3.6.1.4.1.9.9.471 ciscoFlexLinksMIB336 This MIB module is for configuration and status query
of Flex Links feature on the Cisco device.

Flex Links are a pair of Layer 2…
1.3.6.1.4.1.9.9.472 ciscoModuleVirtualizationMIB335 This MIB provides a way to create virtual contexts,
and managing them. A virtual context is logical
partition of a physical devi…
1.3.6.1.4.1.9.9.473 ciscoCcaMIB3200 The Cisco Contact Center Applications (CCCA) Management
Information Base (MIB) module defines management
instrumentation for appl…
1.3.6.1.4.1.9.9.474 ciscoFilterGroupMIB355 The MIB module is for creating and configuring
object groups to support packet filtering and
access control on IP and other proto…
1.3.6.1.4.1.9.9.479 ciscoCableWidebandMIB377 This is the MIB module for the support of Channel Bonding
Protocol for the Cable Modem Termination System (CMTS).

Wideband DOCSIS…
1.3.6.1.4.1.9.9.480 ciscoL4L7moduleResourceLimitMIB4100 The MIB module for managing resource classes
and configuring limits(max/min) to different
resources. The resource referenced in …
1.3.6.1.4.1.9.9.482 ciscoInterfaceTopNExtMIB316 This MIB module is an extension to INTERFACETOPN-MIB.
It provides additional management information for
sorting device interfaces.
1.3.6.1.4.1.9.9.483 ciscoIpRanBackHaulMIB3248 This MIB provides information on the IP-RAN traffic
from cell site to aggregation site in the following
situations. In an GSM en…
1.3.6.1.4.1.9.9.484 ciscoNacNadMIB3157 This MIB module is for the configuration of a Network
Access Device (NAD) on the Cisco Network Admission
Control (NAC) system.

End…
1.3.6.1.4.1.9.9.485 ciscoRttMonTCMIB00 This MIB contains textual conventions used by
CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and
CISCO-RTTMON-ICMP-MIB, but they are not …
1.3.6.1.4.1.9.9.486 ciscoRttMonIcmpMIB37 An extension to the CISCO-RTTMON-MIB for ICMP
operations. The ICMP Jitter operation provides capability
to measure metrics such a…
1.3.6.1.4.1.9.9.487 ciscoRttMonRtpMIB38 An extension to the CISCO-RTTMON-MIB for Cisco IP SLA
RTP operation, Real-Time Transport Protocol(RFC 1889). This
operation provi…
1.3.6.1.4.1.9.9.488 ciscoFirewallTc00 This MIB module defines textual conventions that
are commonly used in modeling management information
pertaining to configuration…
1.3.6.1.4.1.9.9.490 ciscoNetintMIB311 This MIB module is for Network Interrupt information
on Cisco device.
1.3.6.1.4.1.9.9.491 ciscoUnifiedFirewallMIB3360 Overview of Cisco Firewall MIB
==============================
This MIB Module models status and performance
statistics pertaining …
1.3.6.1.4.1.9.9.492 ciscoCefMIB3192 Cisco Express Forwarding (CEF) describes a high speed
switching mechanism that a router uses to forward packets
from the inbound …
1.3.6.1.4.1.9.9.493 ciscoCefTextualConventions00 ciscoCeftextualConventions
1.3.6.1.4.1.9.9.494 ciscoEntityRedunTcMIB00 This module defines the textual conventions used within
Cisco Entity Redundancy MIBs.
1.3.6.1.4.1.9.9.495 ciscoPsdClientMIB344 This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).

This MIB instrumentation is for conf…
1.3.6.1.4.1.9.9.497 cGgsnSAMIB3247 This MIB module manages the service-aware feature of
Gateway GPRS Support Node (GGSN).

This MIB is an enhancement of the CISCO-GG…
1.3.6.1.4.1.9.9.498 ciscoEntityRedunMIB393 This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of c…
1.3.6.1.4.1.9.9.500 ciscoStackWiseMIB3111 This MIB module contain a collection of managed objects
that apply to network devices supporting the Cisco
StackWise(TM) technolo…
1.3.6.1.4.1.9.9.504 ciscoSwitchMulticastMIB3108 This MIB module defines management objects for the
Multicast Switching features on Cisco Layer 2/3
devices.

Definition of some of …
1.3.6.1.4.1.9.9.507 ciscoPolicyGroupMIB335 The MIB module is for configuration of policy and
policy group. A policy group can be described as a set
of entities identified b…
1.3.6.1.4.1.9.9.508 ciscoSlbHealthMonMIB362 An extension to the CISCO-SLB-EXT-MIB for SLB
health monitoring probes.

SLB: Server Load Balancing. Server load balancing
provides…
1.3.6.1.4.1.9.9.509 ciscoWdsInfoMIB3141 This MIB is intended to be implemented on all Cisco
network entities that provide Wireless Domain Services
(WDS). The WDS provide…
1.3.6.1.4.1.9.9.510 ciscoErmMIB, ciscoVoiceLmrMIB3176 This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes …
1.3.6.1.4.1.9.9.511 ciscoCbpTargetTCMIB00 This MIB module defines Textual Conventions for
representing targets which have class based policy
mappings. A target can be any …
1.3.6.1.4.1.9.9.512 ciscoLwappWlanMIB3378 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weigh…
1.3.6.1.4.1.9.9.513 ciscoLwappApMIB51009 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…