Core DB: Per-User Configuration Nodes

Document created by RSA Information Design and Development Employee on Jul 21, 2016
Version 1Show Document
  • View in full screen mode

This topic describes the per-user configuration nodes. There are settings that influence the actions users are allowed to perform on the database. These settings are stored in the configuration tree at /users/accounts/<username>/config, where <username> is the name of the user to which the settings apply.


A query prefix applies a filter to every query operation that the user performs. This is implemented by taking the query.prefix values and appending it the the where clause of each query using the logical && (and) operator. For more information on Where Clauses, see Queries.


This setting is available in Security Analytics 10.4 and earlier versions.

The query.level setting assigns the query level that the users have for every query they perform. These influence whether their queries are limited by the query.level.1.minutes, query.level.2.minutes, or query.level.3.minutes.


This setting is available in Security Analytics 10.5 and later versions.

The query.timeout setting assigns the maximum amount of time in minutes that a user can run each query. For trusted connections, these timeouts are configured on the Security Analytics server. For accounts on Core services, this setting is stored in the configuration tree at /users/accounts/<username>/config, where <username> is the name of the user to which the setting applies. When this value is set to zero, the Core service does not enforce the query timeout.


The session.threshold setting assigns a maximum session threshold for the user. If set, this threshold value is assigned to all values calls that the user performs. A detailed discussion of both the values call and thresholds is covered in this guide.

You are here: Advanced Database Configuration > Per-User Configuration Nodes