SecurityManagement

White List

function description

Allow which client addresses can connect to IoTDB

configuration file

conf/iotdb-common.properties

conf/white.list

configuration item

iotdb-common.properties:

Decide whether to enable white list

# Whether to enable white list
enable_white_list=true

white.list:

Decide which IP addresses can connect to IoTDB

# Support for annotation
# Supports precise matching, one IP per line
10.2.3.4

# Support for * wildcards, one ip per line
10.*.1.3
10.100.0.*

note

1. If the white list itself is cancelled via the session client, the current connection is not immediately disconnected. It is rejected the next time the connection is created.
2. If white.list is modified directly, it takes effect within one minute. If modified via the session client, it takes effect immediately, updating the values in memory and the white.list disk file.
3. Enable the whitelist function, there is no white.list file, start the DB service successfully, however, all connections are rejected.
4. while DB service is running, the white.list file is deleted, and all connections are denied after up to one minute.
5. whether to enable the configuration of the white list function, can be hot loaded.
6. Use the Java native interface to modify the whitelist, must be the root user to modify, reject non-root user to modify; modify the content must be legal, otherwise it will throw a StatementExecutionException.

Audit log

Background of the function

Audit log is the record credentials of a database, which can be queried by the audit log function to ensure information security by various operations such as user add, delete, change and check in the database. With the audit log function of IoTDB, the following scenarios can be achieved:

• We can decide whether to record audit logs according to the source of the link ( human operation or not), such as: non-human operation such as hardware collector write data no need to record audit logs, human operation such as ordinary users through cli, workbench and other tools to operate the data need to record audit logs.
• Filter out system-level write operations, such as those recorded by the IoTDB monitoring system itself.

Scene Description

Logging all operations (add, delete, change, check) of all users

The audit log function traces all user operations in the database. The information recorded should include data operations (add, delete, query) and metadata operations (add, modify, delete, query), client login information (user name, ip address).

Client Sources：

• Cli、workbench、Zeppelin、Grafana、通过 Session/JDBC/MQTT 等协议传入的请求

Audit logging can be turned off for some user connections

No audit logs are required for data written by the hardware collector via Session/JDBC/MQTT if it is a non-human action.

Function Definition

It is available through through configurations:

• Decide whether to enable the audit function or not
• Decide where to output the audit logs, support output to one or more
  1. log file
  2. IoTDB storage
• Decide whether to block the native interface writes to prevent recording too many audit logs to affect performance.
• Decide the content category of the audit log, supporting recording one or more
  1. data addition and deletion operations
  2. data and metadata query operations
  3. metadata class adding, modifying, and deleting operations.

configuration item

In iotdb-engine.properties or iotdb-common.properties, change the following configurations:

####################
### Audit log Configuration
####################

# whether to enable the audit log.
# Datatype: Boolean
# enable_audit_log=false

# Output location of audit logs
# Datatype: String
# IOTDB: the stored time series is: root.__system.audit._{user}
# LOGGER: log_audit.log in the log directory
# audit_log_storage=IOTDB,LOGGER

# whether enable audit log for DML operation of data
# whether enable audit log for DDL operation of schema
# whether enable audit log for QUERY operation of data and schema
# Datatype: String
# audit_log_operation=DML,DDL,QUERY

# whether the local write api records audit logs
# Datatype: Boolean
# This contains Session insert api: insertRecord(s), insertTablet(s),insertRecordsOfOneDevice
# MQTT insert api
# RestAPI insert api
# This parameter will cover the DML in audit_log_operation
# enable_audit_log_for_native_insert_api=true