Electronic Components Datasheet Search
  English  ▼

X  

A30 Datasheet(PDF) 31 Page - NXP Semiconductors

Part # A30
Description  Secure Authenticator
PDF  209 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  NXP [NXP Semiconductors]
Direct Link  http://www.nxp.com
Logo NXP - NXP Semiconductors

A30 Datasheet(HTML) 31 Page - NXP Semiconductors

Back Button A30 Datasheet HTML 27Page - NXP Semiconductors A30 Datasheet HTML 28Page - NXP Semiconductors A30 Datasheet HTML 29Page - NXP Semiconductors A30 Datasheet HTML 30Page - NXP Semiconductors A30 Datasheet HTML 31Page - NXP Semiconductors A30 Datasheet HTML 32Page - NXP Semiconductors A30 Datasheet HTML 33Page - NXP Semiconductors A30 Datasheet HTML 34Page - NXP Semiconductors A30 Datasheet HTML 35Page - NXP Semiconductors Next Button
Zoom Inzoom in Zoom Outzoom out
 31 / 209 page
background image
NXP Semiconductors
A30
Secure Authenticator
The overall command format is outlined in Section 7.3.5 while the two variants are further detailed in the
following subsections.
While the ProcessSM is issued in VCState.AuthenticatedECC, the command itself is not protected by the
regular secure messaging. This means both the command and response are issued in plain, just applying the
secure messaging to the command and response data to support controller device processing.
Once enabled, there is no additional access control to the ProcessSM command. Therefore, it must be
assessed at system level if the access to the command can be abused.
6.3.7.2 ProcessSM_Apply
The ProcessSM_Apply is used for applying secure messaging to a command before sending it to the target
device. The command format is outlined in Section 7.3.6.
If targeting CommMode.Plain, there is no command data exchanged.A30 increments the CmdCtr by the amount
given in CmdCtrIncr. If CmdCtr would reach 0xFFFF or overflow, the command is rejected.
If targeting CommMode.MAC or CommMode.Full, Plaintext provides the data to be protected.
ProcessSM_Apply only supports one-shot operations fitting in a single short-length ISO/IEC 7816-4 APDU.
Bigger lengths are rejected. The data provided and returned by A30 does not hold the ISO/IEC 7816-4 APDU
wrapping overhead. This means the native command fields, as described in Section 6.2.1 consisting of Cmd
(i.e. the ISO/IEC 7816-4 INS field) followed by eventually CmdHeader and CmdData fields (i.e.the full ISO/IEC
7816-4 Command Data field).
If targeting CommMode.Full, an additional parameter Offset indicates where the encryption shall start, i.e.the
first byte of CmdData.
If targeting CommMode.MAC, only the computed MAC is returned. If targeting CommMode.Full, the encrypted
data is returned together with the computed MAC. Other plain data like the Cmd and CmdHeader are not
echoed.
6.3.7.3 ProcessSM_Remove
The ProcessSM_Remove is used for removing and validating secure messaging from a response received from
a target device. The command format is outlined in Section 7.3.7.
If targeting CommMode.Plain, the command must not be called as the only relevant processing (CmdCtr), is
triggered with ProcessSM_Apply.
If targeting CommMode.MAC or CommMode.Full, Ciphertext provides the data to be processed. Note that
ProcessSM_Remove only supports one-shot operations fitting in a single short-length ISO/IEC 7816-4 APDU.
Bigger lengths are rejected. The data provided and returned by A30 does not hold the ISO/IEC 7816-4 APDU
wrapping overhead. This means the native response fields, as described in Section 6.2.1 consisting of RC (i.e.
the ISO/IEC 7816-4 SW2 field) followed by eventually RespData and the MAC (i.e. the full received ISO/IEC
7816-4 Response Data field). In CommMode.Full, RespData is the encrypted response data.
If targeting CommMode.MAC, no data is returned. If targeting CommMode.Full, the decrypted data is returned.
The RC is not echoed.
6.3.8 Secure Dynamic Messaging
The Secure Dynamic Messaging (SDM) allows for confidential and integrity-protected data exchange, without
requiring a preceding authentication. A30 supports SDM for reading from one of the StandardData files on the
PICC. Secure Dynamic Messaging allows adding security to the data read, while still being able to access it
with standard NDEF readers. The typical use case is an NDEF holding a URI and some metadata, where SDM
allows this metadata to be communicated confidentiality and integrity protected toward a back end server.
A30
All information provided in this document is subject to legal disclaimers.
© 2025 NXP B.V. All rights reserved.
Product data sheet
Rev. 3.0 — 27 January 2025
Document feedback
976730
31 / 209



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100  ...More


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com