Engineering references — searchable smart-card, FIDO and V2X PKI databases for the bytes you stare at every day.
18 engineering references — searchable status-word and tag databases for smart-card / FIDO work, plus structured standards summaries for the V2X / ITS PKI stack (IEEE 1609.2, ETSI TS 103 097 / 102 941, ISO 21177, GSMA SGP.32). Client-side search on the database pages; deep-linkable structure on every page. No accounts. No ads. Nothing leaves your browser.
Pair with the tool catalogue when you need to walk live bytes.
V2X / ITS PKI
IEEE 1609.2 V2X Certificates
Certificate structure, COER encoding, IssuerIdentifier, ToBeSignedCertificate fields, signature schemes, and the comparison table with X.509. Pair with the V2X parser tool to walk live bytes.
Structured reference → ETSI TS 103 097ETSI TS 103 097 Secured Messages
SecuredMessage structure, header info fields, signer-info modes (digest, certificate, chain), application profile constraints, and the equivalence with IEEE 1609.2.
Structured reference → ETSI TS 102 941ETSI TS 102 941 Trust & Privacy
V2X PKI hierarchy — Root CA, EA, AA, EC and PC issuance, Butterfly Key Expansion, CRL and CTL distribution. The architectural layer above 1609.2.
Structured reference → ISO 21177ISO 21177 ITS Station Security
ITS-S session-layer security services, secure-session establishment, mutual authentication using 1609.2 certificates. The bridge from V2X PKI into application-layer secure sessions.
Structured reference → GSMA SGP.32GSMA SGP.32 IoT eSIM
eUICC architecture, IPA, SM-DP+, SM-DS, IoT profile-discovery flow, and the parallel to V2X EA / AA lifecycle. The fleet-credential pattern at telecom scale.
Structured reference →Smart-card & APDU protocol
APDU Status Words
ISO/IEC 7816-4 standard status words plus GlobalPlatform, EMV, and FIDO U2F additions. Search by code or by phrase.
48 entries → ISO 7816-4ISO 7816 CLA Values
Common ISO/IEC 7816-4 CLA byte values. Interindustry, proprietary, GlobalPlatform, and secure-messaging variants — with the bit-level breakdown.
10 entries → GlobalPlatform 2.3.1GlobalPlatform Status Words
Status words returned by GlobalPlatform 2.3.1 card-management commands (INSTALL, LOAD, DELETE, GET STATUS, GET DATA). GPC §11.
20 entries → JavaCardJavaCard CAP Components
The 12 component types inside a JavaCard CAP file. Mandatory vs optional, what each carries, and what the on-card verifier checks.
12 entries →ASN.1 & PKI encoding
ASN.1 Universal Tags
Universal-class tag identifiers from ITU-T X.680, with primitive vs constructed form. The encoding floor underneath X.509, PKCS, CMS, FIDO attestation, EMV PKI.
16 entries → X.509 / PKIXX.509 / Certificate OIDs
RDN attribute types (CN, O, C), certificate extensions (KU, EKU, SAN, BC), signature algorithms — the OIDs that appear inside a DER-encoded certificate.
30 entries → X.509 / PKIXX.509 Extensions
Common X.509 v3 extensions — what they are, criticality, and what they encode. Pair with the X.509 viewer to walk live certs.
13 entries →FIDO / WebAuthn
WebAuthn COSE Algorithms
COSE algorithm identifiers used by WebAuthn and FIDO2. ES256 (-7) is the default; EdDSA (-8) and RS256 (-257) appear in older stacks.
FIDO AAGUIDs
Curated AAGUID directory. Search by vendor, model, or AAGUID. Production deployments should fetch the FIDO MDS BLOB for authoritative metadata.
25 entries →EMV & transit
EMV Tags
Searchable EMV tag reference. Books 3, 4, and Contactless. Filter by category to narrow down to the tags you need.
56 entries → NXP DESFireDESFire Status Codes
Documented DESFire EV1/EV2/EV3 response status codes with meaning and context. Search by code or by phrase.
22 entries → NXP DESFireDESFire Command Set
Command name, code, and EV1/EV2/EV3 support, grouped by class. Native and ISO 7816-4 wrapped commands.
64 entries →NFC / NDEF
Where does this run?
Search runs on data shipped with the page. Queries stay local, no logging, no analytics on search terms — privacy-first by design.
Frequently asked questions
What is in the AmbiSecure reference section?
Searchable databases for the values engineers look up repeatedly: APDU status words, EMV tags, ISO 7816 CLA bytes, COSE algorithms, FIDO AAGUIDs, DESFire commands and status, GlobalPlatform status, ASN.1 tags, X.509 extensions and OIDs, and the V2X and eSIM standards.
How is a reference different from a tool?
A reference is a lookup table you search; a tool takes your bytes and decodes them. Most references have a companion tool, and the pages link across to each other.
Are these references authoritative?
No — they are working aids. The standards documents are authoritative, and each page names the specification it summarises so you can check a value against the source.
Do these pages work offline?
Yes. The data ships with the page and searching happens in your browser, so once loaded they keep working without a connection.
How current are these references?
They track the published specifications named on each page. Where a standard has been superseded, the page says so rather than silently presenting the old value.