DbTool Risk Radar Commands
The risk commands run the Risk Radar detectors and produce standalone risk reports.
For how to run DbTool, the common options, and the permissions it requires, see DbTool Command-Line Utility.
risk detectors
Lists every available Risk Radar detector with the ID that the --detectors option of risk report and risk posture requires.
Syntax
DbTool risk detectors
This command has no options other than the Common Options.
risk report
Runs the Risk Radar detectors and writes the results to an HTML report. Every match is reported, including matches already reported by an earlier run.
Syntax
DbTool risk report --file <PATH> [options]
Options
| Option | Description |
|---|---|
--file <PATH>
|
Required. Path of the HTML report to write, for example C:\temp\riskradar.html. |
--days <DAYS>
|
Number of days of audit events the event detectors examine. Default: 1. |
--detectors <IDS>
|
Comma-separated list of detector IDs to run, as shown by risk detectors. Default: every detector. |
--posture
|
Also run the Posture Detectors, which inspect the live directory and DNS rather than stored events. |
--domain <DOMAIN>
|
Domain the posture detectors inspect. Default: the domain this computer belongs to. |
--maximum-findings <COUNT>
|
Maximum number of findings reported by each posture detector, to keep the report readable. Default: 100. |
--dns-servers <SERVERS>
|
Comma-separated list of DNS servers, by address or name, for the posture DNS checks. Default: the name servers of the domain. |
--correlation-source <SOURCE>
|
Where to read Active Directory correlation data from: Live to query Active Directory over LDAP, Sql to read the inventory tables, or SqlIfFresh to use the inventory when it was synchronized recently and query LDAP otherwise. Default: Live. |
Example
DbTool risk report --file C:\temp\riskradar.html --days 7
risk stale-accounts
Scans Active Directory and Entra ID for accounts that have not signed in recently, and writes the results to a CSV file, an HTML report, a PDF report, a webhook, or any combination of these. You must specify at least one output.
Syntax
DbTool risk stale-accounts --days <DAYS> [options]
Options
| Option | Description |
|---|---|
--days <DAYS>
|
Required. Number of days without a successful sign-in after which an account is considered stale. |
--csv <PATH>
|
Path of a CSV file to write the results to. |
--html <PATH>
|
Path of an HTML report to write the results to. |
--pdf <PATH>
|
Path of a PDF report to write the results to. |
--pdf-landscape
|
Use landscape orientation for the PDF report, which fits more columns on each page. Default: portrait. |
--webhook-url <URL>
|
HTTPS endpoint to send each stale account to, as one JSON payload per account (POST request). |
--allow-untrusted
|
Send to --webhook-url even when its TLS certificate is self-signed, expired, or otherwise untrusted. |
--no-unused
|
Exclude accounts that have never signed in, so that the results include only accounts that became stale. |
Example
DbTool risk stale-accounts --days 90 --html C:\temp\stale.html
risk posture
Runs the Posture Detectors against the Active Directory inventory and records a snapshot for the risk dashboard, in the same way as the scheduled posture job.
Syntax
DbTool risk posture [options]
Options
| Option | Description |
|---|---|
--domain <DOMAIN>
|
Run the detectors for this domain only. Default: every domain in the Active Directory inventory. |
--detectors <IDS>
|
Comma-separated list of detector IDs to run, as shown by risk detectors. Default: every posture detector. |
--dry-run
|
Run the detectors and display the statistics without writing anything to the database. |
--empty-findings
|
Include detectors that produced no findings in the displayed details. |
Example
DbTool risk posture --dry-run