...
| ID | Type | Field Name | Description | Reference |
|---|---|---|---|---|
| CON-LOG-REQ-7 | REQUIRED | date/time | The container and container application MUST log the field “date/time” in the security audit logs. The value should be represented in UTC and formatted per ISO 8601, such as “2015-06-03T13:21:58+00:00”. The time should be shown with the maximum resolution available to the logging component (e.g., milliseconds, microseconds) by including the appropriate number of decimal digits. For example, when millisecond precision is available, the date-time value would be presented as, as “2015-06-03T13:21:58.340+00:00”. | |
CON-LOG-REQ-8 | REQUIRED | protocol | The container and container application MUST log the field “protocol” in the security audit logs. What are you trying to do. What URL were you trying to hit when doing this. Could be presented as an enum (HTTP, HTTPS, SSH, etc). THis is the OSI application layer protocol. This is the communication mechanism. | |
CON-LOG-REQ-9 | REQUIRED | Service / Program Name | The container and container application MUST log the field “service or program used for access” in the security audit logs. ServiceName: The URI that the caller used to make the call to the component that is logging the message. (The service inside the partner doing the call - includes API name) The service name Endpoint., (Were they are connecting too) This is represented as a URL or URI. | |
CON-LOG-REQ-10 | REQUIRED | Status Code | The container and container application MUST log the field “success/failure” in the security audit logs. StatusCode: This field indicates the high level status of the request - one of (COMPLETE, ERROR, INPROGRESS) This is meant for transactional events. | |
| CON-LOG-REQ-11 | REQUIRED | Principal ID |
The container and container application MUST log the Principal identity of the entity accessing the service (e.g., Log ID, NPE, Token, etc.) | R-89474 |
| CON-LOG-REQ-MP12 | REQUIRED | Group ID | The container and container application MUST log the Group ID of the Principal identity of the entity accessing the service Note: The group ID is in reference to a Role or Attribute as part of a RBAC or ABAC scheme. Should we call this something else? Potential confusion since Group ID is overloaded term. **This needs additional discussion | N/A |
| CON-LOG-REQ-MP01 | Container ID | Container ID; unique for life time of the system, for the instance, once container is killed, this ID goes away | ||
| CON-LOG-REQ-MP02 | Container Name | Container Name; unique name of the image ( webserver, FW, DCAE01) | ||
| CON-LOG-REQ-MP03 | Contaimer Image Hash | Container Image Name (Hash); Image name and Hash ( container lifecycle events | ||
| CON-LOG-REQ-MP04 | REQUIRED | Log Level | "The VNF SHOULD use an appropriately configured logging level that can be changed dynamically, so as to not cause performance degradation of the VNF due to excessive logging." Logging Level Follows Syslog levels numbered 0 - 7; (Emergency, Alert, Criticial, Error, Warning, Notification, Informational, Debugging) | R-28168 |
| CON-LOG-REQ-MP11 | Image ID Image Hash | The container MUST log the image ID and layer hash | T1036, T1525 | |
| CON-LOG-REQ-MP13 | RequestID | To support flow tracking across ONAP components a container MUST log RequestID RequestID: UUID to track the processing of each client request across all the ONAP components involved in its processing | v1.3 Spec | |
| Severity | Severity level? {Major, Minor, Critical} : For error reporting on internal processing |
...