You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: doc/audit/security_auditing_HLD.md
+78-86
Original file line number
Diff line number
Diff line change
@@ -120,141 +120,133 @@ Examples:
120
120
121
121
### 3.3 Configuration design
122
122
#### 3.3.1 ConfigDB schema
123
-
##### 3.3.1.1 AUDIT TABLE
124
-
The database to be used is Config DB. A new AUDIT table will be added to the Config DB, which is responsible for storing audit configuration settings. This table allows the system to manage security auditing by defining whether auditing is enabled and specifying the rules to be applied. The structure of the AUDIT table is as follows.
123
+
##### 3.3.1.1 AUDITD TABLE
124
+
The database to be used is Config DB. A new AUDITD table will be added to the Config DB, which is responsible for storing auditd configuration settings. This table allows the system to manage security auditing by defining whether auditing is enabled and specifying the rules to be applied. The structure of the AUDITD table is as follows.
125
125
```
126
126
; Defines audit configuration information
127
-
key = AUDIT|config ; Audit configuration settings
127
+
key = AUDITD ; Audit configuration settings
128
128
; field = value
129
-
groupid = 1*255VCHAR ; Name of the audit rule group
130
-
groupvalue = enabled / disabled ; Indicates whether the entire audit rule group is enabled or disabled
129
+
name = 1*255VCHAR ; Name of the audit rule group
130
+
state = enabled / disabled ; Indicates whether the entire audit rule group is enabled or disabled
131
131
```
132
132
133
133
##### 3.3.1.2 Config DB JSON Sample
134
134
The predefined list of rules in Section 3.2 will be **enabled** by default, while the custom user-defined group will be **disabled** by default. Below is an example of how the audit rules could be represented in JSON format within the Config DB.
135
135
```
136
136
{
137
-
"AUDIT": {
138
-
"config": {
139
-
"critical_files": "enabled",
140
-
"dns_changes": "enabled",
141
-
"time_changes": "enabled",
142
-
"shutdown_reboot": "enabled",
143
-
"cron_changes": "enabled",
144
-
"modules_changes": "enabled",
145
-
"auth_logs": "enabled",
146
-
"bin_changes": "enabled",
147
-
"user_group_management": "enabled",
148
-
"file_deletion": "enabled",
149
-
"log_changes": "enabled",
150
-
"docker_changes": "enabled",
151
-
"process_audit": "enabled",
152
-
"network_activity": "enabled",
153
-
"socket_activity": "enabled",
154
-
"custom_audit": "disabled"
137
+
"AUDITD": {
138
+
"critical_files": {
139
+
"state": "enabled"
140
+
},
141
+
"dns_changes": {
142
+
"state": "enabled"
143
+
},
144
+
"time_changes": {
145
+
"state": "enabled"
146
+
},
147
+
"shutdown_reboot": {
148
+
"state": "enabled"
149
+
},
150
+
"cron_changes": {
151
+
"state": "enabled"
152
+
},
153
+
"modules_changes": {
154
+
"state": "enabled"
155
+
},
156
+
"auth_logs": {
157
+
"state": "enabled"
158
+
},
159
+
"bin_changes": {
160
+
"state": "enabled"
161
+
},
162
+
"user_group_management": {
163
+
"state": "enabled"
164
+
},
165
+
"file_deletion": {
166
+
"state": "enabled"
167
+
},
168
+
"log_changes": {
169
+
"state": "enabled"
170
+
},
171
+
"docker_changes": {
172
+
"state": "enabled"
173
+
},
174
+
"process_audit": {
175
+
"state": "enabled"
176
+
},
177
+
"network_activity": {
178
+
"state": "enabled"
179
+
},
180
+
"socket_activity": {
181
+
"state": "enabled"
182
+
},
183
+
"custom_audit": {
184
+
"state": "disabled"
155
185
}
156
186
}
157
187
}
158
188
```
159
189
160
190
##### 3.3.1.3 Redis Entries Sample
161
-
Once the AUDIT table is populated in the Config DB, the corresponding entries can be viewed in Redis. Below are complete example Redis commands and outputs
191
+
Once the AUDITD table is populated in the Config DB, the corresponding entries can be viewed in Redis. Below are complete example Redis commands and outputs
0 commit comments