Audit Logging

The server now has the ability to produce audit logs of all user activity on the system. This will produce an auditable trail of user session events, and access and modification of all entities in the system. These audit logs will be output to the standard out for the docker container and can be routed into a log aggregation system.
In order to use audit logging you will need to contact your sales representative and have the Security and Compliance package added to your license.
The data in the logs is presented in the following format:
1
date EVENT uuid projectId sessionId userId [additional information]
Copied!
You can turn off audit logging by setting the NOAUDITLOG flag to true in the .env file or in docker secrets.
Audit Logging Events
There are a number of events that are tracked when audit logging is enabled. The following outlines these events that are logged.
Aggregation System Deployment
There are special aggregation systems that help to aggregate and manage your Docker logs. In this article we will consider connection using the open source Elastic Stack log analysis software as an example.
The Elastic Stack consists of two different tools: Elasticsearch and Kibana. Elasticsearch is needed to store log data and Kibana to visualize it. In order to transfer the logs into ElasticSearch we will use the open source data shipper FileBeat.
There are many ways to set up the Elastic Stack, the easiest is using docker-compose. We will use the official docker images and there will be a single ElasticSearch node.
Step 1: Add the following rows to the existing docker-compose.yml:
1
services:
2
  elasticsearch:
3
    image: "docker.elastic.co/elasticsearch/elasticsearch:7.2.0"
4
    environment:
5
        - "ES_JAVA_OPTS=-Xms1g -Xmx1g"
6
        - "discovery.type=single-node"
7
    ports:
8
        - "9200:9200"
9
    volumes:
10
        - elasticsearch_data:/usr/share/elasticsearch/data
11
​
12
  kibana:
13
      image: "docker.elastic.co/kibana/kibana:7.2.0"
14
      ports:
15
          - "5601:5601"
16
​
17
  filebeat:
18
      image: "docker.elastic.co/beats/filebeat:7.2.0"
19
      user: root
20
      volumes:
21
          - /MY_WORKDIR/filebeat.yml:/usr/share/filebeat/filebeat.yml:ro
22
          - /var/lib/docker:/var/lib/docker:ro
23
          - /var/run/docker.sock:/var/run/docker.sock
24
volumes:
25
  mdb-data:
26
  elasticsearch_data:
Copied!
Note that you need to replace MY_WORKDIR with the path of your working directory.
For ElasticSearch and Kibana basic docker configuration is enough. They are respectively available on ports 9200 and 5601. ElasticSearch has a volume to keep its data. Kibana doesn't need a volume as it uses ElasticSearch to persist its configuration. FileBeat, on the other hand, needs to be configured. To share this config file with the container, we need a read-only volume /usr/share/filebeat/filebeat.yml:ro. FileBeat also needs to have access to docker log files. They can usually be found in /var/lib/docker/containers but that might depend on your docker installation. The docker socket /var/run/docker.sock is also shared with the container. That allows FileBeat to use the docker daemon to retrieve information and enrich the logs with things that are not directly in the log files, such as the name of the image or the name of the container.
Step 2: 
Create the filebeat configuration file in /MY_WORKDIR/filebeat.yml
1
filebeat.inputs: 
2
  - 
3
    paths:
4
      - /var/lib/docker/containers/*/*.log
5
    type: container
6
logging.json: true
7
logging.metrics.enabled: false
8
output.elasticsearch: 
9
  hosts: 
10
    - "elasticsearch:9200"
11
  indices: 
12
    - 
13
      index: "filebeat-%{[agent.version]}-%{+yyyy.MM.dd}"
14
processors: 
15
  - 
16
    add_docker_metadata: 
17
      host: "unix:///var/run/docker.sock"
18
  - 
19
    decode_json_fields: 
20
      fields: 
21
        - message
22
      overwrite_keys: true
23
      target: json
Copied!
The FileBeat input type container is needed to import logs from docker. /var/lib/docker/containers/*/*.log is the location of the log files inside the FileBeat container.
The output elasticsearch setting allows you to configure the ElasticSearch address as well as the indexes where the logs are imported. The template index filebeat-%{[agent.version]}-%{+yyyy.MM.dd} includes a date. This means that docker logs are imported into the index corresponding to the date they appeared.
add_docker_metadata is needed in order to add useful information to the logs, such as the name of the image or the name of the container. Only ids are displayed by default.
decode_json_fields lets to parse logs encoded in JSON. The logs in FileBeat, ElasticSearch and Kibana consists of multiple fields. The message field is what the application (running inside a docker container) writes to the standard output.
Step 3: Launch docker containers with docker-compose
Kibana is now available on http://localhost:5601. Click on the left on Discover and on Create Index Pattern. Create a pattern using filebeat-* (to include all logs from FileBeat) and @timestamp.
Done! Click on Discover again and you will see the logs. Note that logs of all containers are displayed with default configuration. The formio logs described at the beginning of this article come from the formio container.

Developer Guide - Previous

RTL Forms

Next - Developer Guide

Form.io CLI Tool

Last modified 4mo ago

Copy link

Contents

Audit Logging Events

Aggregation System Deployment