Konica Minolta bizhub PRO C1060L bizhub PRESS C1070/C1070P/C1060/bizhub PRO C1 - Page 32

Specifying unauthorized actions: password authentication, Specifying unauthorized actions: actions - specifications

Page 32 highlights

2 2-24 Administrator Security Functions 2.3 No. Operation Audit ID 10 Change user attribute by administrator User ID 11 Password authentication for user User ID*1/Unregistered user ID*2 12 Change attributes of user by user (user User ID password, etc.) 13 Change HDD lock password Administrator ID 14 (not used) 15 Access to stored job User ID (Printing hold/HDD store job, recalling HDD store job to hold job, storing hold job on HDD) 16 Delete store job User ID Stored action 10 11 Result OK OK/NG 12 OK 19 OK 15 OK 16 OK *1: Audit log ID is saved as user ID when user authentication is successfully made, or when password inconformity occurs with a registered user name. *2: Audit log ID is saved as unregistered user ID when authentication failure occurs with an unregistered user name. The purpose of analyzing the audit log is to understand the following and implement countermeasures: - Whether or not data was accessed or tampered with - Subject of attack - Details of attack - Result of attack For specific analysis methods, refer to the following description. Specifying unauthorized actions: password authentication If logs have NG as the result of password authentication (action: 01, 02, 11), items protected by passwords may have been attacked. - Failed password authentication (NG) log entries specify who made the operation, and show if unauthor- ized actions were made when password authentication failed. - Even if password authentication succeeded (OK), you may need to check whether a legitimate user cre- ated the action. Careful check is recommended especially when successful authentication occurs after series of failures, or for those made during times other than normal operating hours. Specifying unauthorized actions: actions other than password authentication Since all operation results other than password authentication are indicated as successful (OK), use ID and action to determine if any unauthorized actions were made. - Since you cannot identify what was attacked only with an ID, you need to refer to the correspondence table of actions on the previous page to determine whether unauthorized actions were made on a personal box or secure box. - Check the time of operation, and see if the user who operated the specific subject made any unauthorized actions. For example: If a document saved in a box is printed with fraudulent authentication, the following audit log entry will be created. 1. Password authentication to the box: action = 11 id = Box for which the authentication was performed result = OK/NG 2. Access to the document in the box: action = 13 bizhub PRESS C1070/C1070P/C1060, bizhub PRO C1060L

  • 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

Administrator Security Functions
2
2-24
bizhub PRESS C1070/C1070P/C1060, bizhub PRO C1060L
2.3
*1
: Audit log ID is saved as user ID when user authentication is successfully made, or when password incon-
formity occurs with a registered user name.
*2
: Audit log ID is saved as unregistered user ID when authentication failure occurs with an unregistered user
name.
The purpose of analyzing the audit log is to understand the following and implement countermeasures:
-
Whether or not data was accessed or tampered with
-
Subject of attack
-
Details of attack
-
Result of attack
For specific analysis methods, refer to the following description.
Specifying unauthorized actions: password authentication
If logs have NG as the result of password authentication (action: 01, 02, 11), items protected by passwords
may have been attacked.
-
Failed password authentication (NG) log entries specify who made the operation, and show if unauthor-
ized actions were made when password authentication failed.
-
Even if password authentication succeeded (OK), you may need to check whether a legitimate user cre-
ated the action. Careful check is recommended especially when successful authentication occurs after
series of failures, or for those made during times other than normal operating hours.
Specifying unauthorized actions: actions other than password authentica-
tion
Since all operation results other than password authentication are indicated as successful (OK), use ID and
action to determine if any unauthorized actions were made.
-
Since you cannot identify what was attacked only with an ID, you need to refer to the correspondence
table of actions on the previous page to determine whether unauthorized actions were made on a per-
sonal box or secure box.
-
Check the time of operation, and see if the user who operated the specific subject made any unauthor-
ized actions.
For example:
If a document saved in a box is printed with fraudulent authentication, the following audit log entry will be
created.
1. Password authentication to the box:
action = 11
id = Box for which the authentication was performed
result = OK/NG
2. Access to the document in the box:
action = 13
10
Change user attribute by administrator
User ID
10
OK
11
Password authentication for user
User ID
*1
/Unregistered
user ID
*2
11
OK/NG
12
Change attributes of user by user (user
password, etc.)
User ID
12
OK
13
Change HDD lock password
Administrator ID
19
OK
14
(not used)
15
Access to stored job
(Printing hold/HDD store job, recalling
HDD store job to hold job, storing hold
job on HDD)
User ID
15
OK
16
Delete store job
User ID
16
OK
No.
Operation
Audit ID
Stored ac-
tion
Result