File: rule.yml

package info (click to toggle)
scap-security-guide 0.1.78-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 114,600 kB
  • sloc: xml: 245,305; sh: 84,381; python: 33,093; makefile: 27
file content (38 lines) | stat: -rw-r--r-- 1,423 bytes parent folder | download | duplicates (2)
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

title: Ensure that OpenShift Logging Operator is scanning the cluster

description: |-
  OpenShift Logging Operator provides ability to aggregate all the logs from the
  OpenShift Container Platform cluster, such as node system audit logs, application
  container logs, and infrastructure logs. OpenShift Logging aggregates these logs
  from throughout OpenShift cluster and stores them in a default log store. [1]

  [1]https://docs.openshift.com/container-platform/latest/observability/logging/logging-6.0/log6x-about.html

rationale: |-
  OpenShift Logging Operator is able to collect, aggregate, and manage logs.

identifiers:
  cce@ocp4: CCE-85918-1

references:
  nist: AU-3(2)
  srg: SRG-APP-000092-CTR-000165,SRG-APP-000111-CTR-000220,SRG-APP-000358-CTR-000805

ocil_clause: 'OpenShift Logging Operator is not installed'

ocil: |-
    Run the following command to retrieve the clusterlogforwarder objects in the system:
    <pre>$ oc get clusterlogforwarder --all-namespaces</pre>
    Make sure the OpenShift Logging Operator is installed and there exists
    at least one active clusterlogforwarder object in the cluster.

severity: medium


warnings:
- general: |-
    {{{ openshift_cluster_setting([
      "/apis/logging.openshift.io/v1/namespaces/openshift-logging/clusterloggings/instance",
      "/apis/observability.openshift.io/v1/namespaces/openshift-logging/clusterlogforwarders",
    ]) | indent(4) }}}