E-Payment
MagIC
3
X-series - MAINTENANCE MANUAL
Chapter 2 :
TROUBLESHOOTING
Ref: 22000-00-MAN-I-09004
June 2009
Ch.2 - 36/37
Copyright Gemalto – 2008
No disclosure to a third party without prior written consent of Gemalto
Some other examples :
SP Status
2
SECURITY ALERT
UKSR (Sav)
0
1
00 00 00
= UKSR (Curr)
UKSR (Curr)
0
1
00 00 01
The root cause is the mesh
SECIRQ (Sav
xx xx xx xx
NOT RELEVANT
SECIRQ (Cur) 0
0
00 00 00
The issue on the mesh has disappeared
SP Status
2
SECURITY ALERT
UKSR (Sav)
0
3
00 00 00
= UKSR (Curr)
UKSR (Curr)
0
3
00 00 01
The root cause is a mesh + switch(es)
SECIRQ (Sav
xx xx xx xx
NOT RELEVANT
SECIRQ (Cur) 0
2
00 00 00
The issue on the switch is still present, but not on the mesh
SP Status
0
SECURITY is Ok (AUTH_SP & AUTH_CUST have been loaded and Terminal
is not tampered)
UKSR (Sav)
0
2
00 00 00
We can see that the last SECURITY ALERT was due to a switch
UKSR (Curr)
00 00 00 0
1
No attack since last unlock
SECIRQ (Sav
xx xx xx xx
NOT RELEVANT
SECIRQ (Cur) 00 00 00 00
All security triggers are currently Ok
SP Status
2
SECURITY ALERT
UKSR (Sav)
01 00 00 00
Not relevant in this example
UKSR (Curr)
00 00 00 0
3
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.
SECIRQ (Sav
xx xx xx xx
NOT RELEVANT
SECIRQ (Cur) xx xx xx xx
Not relevant in this example
SP Status
2
SECURITY ALERT
UKSR (Sav)
00 0
8
00 00
= UKSR (Curr)
UKSR (Curr)
00 0
8
00 01
The root cause is the lithium cell voltage.
SECIRQ (Sav
xx xx xx xx
NOT RELEVANT
SECIRQ (Cur) 00 0
8
00 00
The issue is still present
bit0 of UKSR (Saved) is always 0