eMAPT study guide
eMAPT · Work through your exam, one topic at a time.
The eMAPT page on INE's site currently returns a 404 and redirects to the INE homepage, so no verified statement of the credential's scope, format, length, passing score, fee, retake policy, or validity period is available. The only substantive material the retrieved page carries is a technical write-up filed under the category "PKI / TLS / applied cryptography," which is the single domain reflected in this profile. That write-up is a walkthrough of the INE Skill Dive lab "GhostTrust: Certificate Forgery and TLS Trust Abuse," built around the October 2026 eMudhra incident in which eight intermediate CA private keys were recoverable because their P-384 private scalars came from a catastrophically small candidate space. Candidates preparing in this domain should be able to explain the chain of trust from root to intermediate to leaf, why a mathematically valid signature can still represent a forged identity, how low-entropy key generation collapses the discrete-log assumption, and why a stale trust bundle in non-browser software outlives browser blocklists. Practical preparation means working hands-on with certificate inspection, key recovery against deliberately weak keys, unauthorized leaf issuance, and comparing legacy versus patched trust policies. Treat every administrative detail as unconfirmed until INE publishes a working certification page. Topics on this exam: PKI / TLS / applied cryptography. The eMAPT study guide has 1 section and about 1,221 words.
01PKI: Chains, Trust Anchors, and Pinning on Mobile
PKI questions on eMAPT focus on how a mobile OS decides to trust a server certificate and what that means for interception testing. You are expected to trace a chain, name the fields that decide the outcome, and explain why installing a proxy CA frequently fails. A certificate is only as trusted as the path from leaf to a trust anchor in the platform store. Every link's signature, validity window, and issuer/subject match must verify.
1,221 words, about 6 minMore study resources for eMAPT
- Practice questionsIn a TLS 1.3 handshake, which key exchange mechanism is used to establish the shared secret that protects application data?
- FlashcardsX.509 TBS portion. The to-be-signed fields of a certificate (version, serial, algorithms, issuer, validity, subject, SPKI, extensions) that the CA signs; the signature itself is excluded.
- Cheat sheetX.509 v3 certificate fields: version, serialNumber, signatureAlgorithm, issuer, validity (notBefore/notAfter), subject, subjectPublicKeyInfo, extensions, and the CA's signature over the TBS (to-be-signed) portion.
- Key termsPlaintext. The original, readable form of data before any encryption or encoding is applied.
- Study planMap the PKI trust chain from root CA to leaf to end entity, and explain each certificate field and extension (Basic Constraints, Key Usage, EKU, SAN, AIA, CRLDP) in your own words.
- Common mistakesCandidates focus on the single certificate shown and forget that trust is transitive; a leaf signed by an intermediate proves nothing unless that intermediate itself chains to an anchor in the trust store, and each signature plus validity window must hold.
- Exam-day guideBring the original, unexpired ID whose name matches your registration exactly.