Gemalto MagIC3 C-series Maintenance Manual page 31

E-Payment
Some other examples :
2
SP Status
UKSR (Sav) 01 00 00 00
UKSR (Curr) 01 00 00 01
SECIRQ (Sav xx xx xx xx
SECIRQ (Cur) 00 00 00 00
2
SP Status
UKSR (Sav) 03 00 00 00
UKSR (Curr) 03 00 00 01
SECIRQ (Sav xx xx xx xx
SECIRQ (Cur) 02 00 00 00
0
SP Status
UKSR (Sav) 02 00 00 00
UKSR (Curr) 00 00 00 01
SECIRQ (Sav xx xx xx xx
SECIRQ (Cur) 00 00 00 00
2
SP Status
UKSR (Sav) 01 00 00 00
UKSR (Curr) 00 00 00 03
SECIRQ (Sav xx xx xx xx
SECIRQ (Cur) xx xx xx xx
SP Status 2
UKSR (Sav) 00 08 00 00
UKSR (Curr) 00 08 00 01
SECIRQ (Sav xx xx xx xx
SECIRQ (Cur) 00 08 00 00
SP Status 2
UKSR (Sav) 00 00 00 08
UKSR (Curr) 00 00 00 09
SECIRQ (Sav xx xx xx xx
SECIRQ (Cur) xx xx xx xx
bit0 of UKSR (Saved) is always 0
5
Remember, on this Terminal, some switches and meshs are interlaced by design. It means that when the
Secure Processor records a mesh issue, the root cause can be also one of the switches.
Ref: 22000-01-MAN-I-09010
Copyright Gemalto – 2009
3
MagIC C-series - MAINTENANCE MANUAL
Chapter 2 : TROUBLESHOOTING
SECURITY ALERT
= UKSR (Curr)
The root cause is the mesh (
NOT RELEVANT
The issue on the mesh has disappeared
SECURITY ALERT
= UKSR (Curr)
The root cause is a mesh + switch(es)
NOT RELEVANT
The issue on the switch is still present, but not on the mesh
SECURITY is Ok (AUTH_SP & AUTH_CUST have been loaded and terminal
is not tampered)
We can see that the last SECURITY ALERT was due to a switch
No attack since last unlock
NOT RELEVANT
All security triggers are currently Ok
SECURITY ALERT
Not relevant in this example
Here we can see that SOFT is set, it means that the terminal underwent a
RESET process, and that since this operation, AUTH_SP & AUTH_CUST
keys have not been reloaded.
NOT RELEVANT
Not relevant in this example
SECURITY ALERT
= UKSR (Curr)
The root cause is the lithium cell voltage.
NOT RELEVANT
The issue is still present
SECURITY ALERT
= UKSR (Curr)
The terminal has been open
NOT RELEVANT
Not relevant in this example
Sept 2009
No disclosure to a third party without prior written consent of Gemalto
5
)
Ch.2 - 31/32