> For the complete documentation index, see [llms.txt](https://docs.enginsight.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enginsight.com/docs/manual/english/platform-usage/penetration-testing/management/audit-definitions/add-audit-definition.md).

# Add Audit Definition

<i class="fa-computer-mouse">:computer-mouse:</i> Click <i class="fa-plus">:plus:</i> **Create Audit Definition** in the upper-right corner to create a new audit definition for a penetration test. The **Penetration Tests** → **Audit Definitions** → **Add** view opens.

<figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FjThMh5YHYUQo9RVmBTTO%2Fenginsight-screenshot-penetrations%20testing-management-audit%20definitions-add%20audit%20defintion.jpg?alt=media&amp;token=50f49f4c-bceb-4b9e-8076-4e602f7e6e91" alt=""><figcaption></figcaption></figure>

<i class="fa-computer-mouse">:computer-mouse:</i> After configuring all settings, click **Create Audit Definition** to add a new audit template.

<i class="fa-computer-mouse">:computer-mouse:</i> Click **Back** to return to the overview.

{% hint style="danger" %}
**Please note**: If you leave this view without clicking **Create Audit Definition**, all configured settings will be lost and cannot be recovered.
{% endhint %}

***

## General Settings

Here you can configure various basic settings.

<figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FGtLHhJSJhRUQuEpCM3BP%2Fenginsight-screenshot-penetrations%20testing-management-audit%20definitions-add%20audit%20defintion-general%20settings.jpg?alt=media&amp;token=de9229e7-b60b-480b-8437-9bfa847ccb6a" alt=""><figcaption></figcaption></figure>

The following options are available:

<table><thead><tr><th width="199.6875">Option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Enter a meaningful name for the audit definition.</td></tr><tr><td>Description</td><td><p>Provide a more detailed description for the audit definition.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>This field is optional.</p></div></td></tr><tr><td>Hacktor</td><td><p>Select a <a href="/docs/manual/english/installation-and-configuration/installation-and-configuration/enginsight-components/hacktor.md">Hacktor</a> that should attack the selected target systems.</p><div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p><strong>Please note</strong>: The host on which Hacktor is installed must be able to communicate with the selected target systems. Check your firewall settings if necessary and create a <a href="/docs/manual/english/platform-usage/hosts/intrusion-detection-system/whitelist/add-whitelist-entry.md">whitelist entry for Hacktor in the Intrusion Detection System (IDS)</a>.</p></div><p><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Hacktor</strong> field to expand a list of all available Hacktors, and select a Hacktor. Alternatively, use the free-text input to find a Hacktor in the list more quickly.<br><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Remove</strong> icon <i class="fa-circle-xmark">:circle-xmark:</i> next to an added Hacktor to remove it from the <strong>Hacktor</strong> field.</p></td></tr><tr><td>Target Groups</td><td><p>Select the <a href="/docs/manual/english/platform-usage/penetration-testing/management/target-groups.md">target groups</a> that should be attacked by the selected Hacktor.</p><p></p><p><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Target Groups</strong> field to expand a list of all available target groups, and select one or more target groups. Alternatively, use the free-text input to find target groups in the list more quickly.<br><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Remove</strong> icon <i class="fa-circle-xmark">:circle-xmark:</i> next to an added target group to remove it from the <strong>Target Groups</strong> field.</p></td></tr><tr><td>Auth-Providers</td><td><p>Select <a href="/docs/manual/english/platform-usage/penetration-testing/management/auth-providers.md">custom authentication providers</a> that provide access to password-protected systems.</p><p></p><p><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Auth-Providers</strong> field to expand a list of all available authentication providers, and select one or more providers from the list. Alternatively, use the free-text input to find providers in the list more quickly.<br><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Remove</strong> icon <i class="fa-circle-xmark">:circle-xmark:</i> next to an added provider to remove it from the <strong>Auth-Providers</strong> field.</p></td></tr></tbody></table>

***

## Recurring Execution

Here you can configure a penetration test to run regularly based on the audit definition at a custom interval and automatically send a report by email.

{% hint style="warning" %}
**Please note**: Audits can be started through a recurring execution **no more frequently than every 3 hours**.
{% endhint %}

<i class="fa-computer-mouse">:computer-mouse:</i> Click the **Recurring Execution** field to show the [Scheduled Execution option](#scheduled-execution) and the [Send by Email option](#send-by-email).

<figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FFOzvTRAoxUh7xxWRAgZG%2Fenginsight-screenshot-penetrations%20testing-management-audit%20definitions-add%20audit%20defintion-recurring%20execution.jpg?alt=media&amp;token=21fd052f-e85a-4359-90bc-8caef0ca3166" alt=""><figcaption></figcaption></figure>

The following options are available:

{% tabs %}
{% tab title="Scheduled Execution" %} <i class="fa-computer-mouse">:computer-mouse:</i> Select the checkbox <i class="fa-square">:square:</i> next to **Scheduled Execution** to run the penetration test regularly based on the audit definition at a specified interval. The time interval selection opens, allowing you to create a custom execution schedule.

#### Time Interval Selection

<div align="left"><figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FRsieOenWTuTSSsvDverr%2FEnginsight-EN-SIEM-Time%20Interval%20Selection.jpg?alt=media&amp;token=12622f35-614f-484b-b6c7-68e059b43e9d" alt="" width="527"><figcaption></figcaption></figure></div>

The following options are available:

<table><thead><tr><th width="199.9140625">Option</th><th>Description</th></tr></thead><tbody><tr><td>Time Zone</td><td><p>Define the time zone that you want to use for the selected time interval.</p><p></p><p><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Time Zone</strong> field to expand a list of all available time zones, and select a time zone.</p></td></tr><tr><td>Cron Expression (Vixie/Unix)</td><td>Shows the defined interval as a cron expression. The cron expression is updated automatically whenever you configure a time interval manually.<br><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Cron Expression</strong> field to <a href="/docs/manual/english/appendix/angabe-von-cron-ausdruecken.md">edit the cron expression manually</a>.</td></tr><tr><td>Next Execution (Local Time Zone)</td><td>Shows the exact date and time of the next execution in your <em>browser’s local time zone</em>.</td></tr><tr><td>Description</td><td>Shows the defined interval for recurring execution as a plain-language description.</td></tr><tr><td>Time Interval Selection</td><td><p>Define a custom execution interval.</p><p><br>Select the relevant minutes, hours, days of the month, months, or days of the week.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Send by Email" %} <i class="fa-eye">:eye:</i> This section is only visible if **Scheduled Execution** is enabled.

<figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FG5oWlzfKQXDupdXh35i3%2Fenginsight-screenshot-penetrations%20testing-management-audit%20definitions-add%20audit%20defintion-send%20by%20email.jpg?alt=media&amp;token=11d29e9e-196c-46f0-966b-7db6ccdaa86a" alt=""><figcaption></figcaption></figure>

<i class="fa-computer-mouse">:computer-mouse:</i> Select the checkbox <i class="fa-square">:square:</i> next to **Send by Email** to automatically send the audit report by email to selected team members after an audit is completed.

<table><thead><tr><th width="200.10546875">Option</th><th width="497.89453125">Description</th></tr></thead><tbody><tr><td>Type</td><td><p>Define the file format in which the audit report should be sent.</p><p></p><p>The following options are available:</p><ul><li><strong>DOCX</strong>: The report is sent in DOCX format for Microsoft Word and compatible office applications.</li><li><strong>PDF</strong>: The report is sent in PDF format.</li></ul><p><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Type</strong> field to expand a list of all available file types, and select a type.</p></td></tr><tr><td>Allowed Members</td><td>Define which team members should receive the audit report by email.<br><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Allowed Members</strong> field to expand a list of all available users.<br><br><i class="fa-computer-mouse">:computer-mouse:</i> Click the <strong>Remove</strong> icon <i class="fa-circle-xmark">:circle-xmark:</i> next to an added user to remove them from the <strong>Allowed Members</strong> field.</td></tr><tr><td>Password</td><td><p>Enter the password recipients must use to open the encrypted audit report.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>This field is optional.</p></div><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Please note</strong>: If you do not enter a password, the document is sent without encryption. However, we strongly recommend that you send the document in encrypted form.</p></div></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

## Advanced Settings

Here you can select all attack methods that Hacktor should use to attack the target systems.

<figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FDSZRoVZ2foqUc0wr5kxB%2Fenginsight-screenshot-penetrations%20testing-management-audit%20definitions-add%20audit%20defintion-advanced%20settings.jpg?alt=media&amp;token=a89bde84-547d-4369-a5cd-63c3e7466bdf" alt=""><figcaption></figcaption></figure>

<i class="fa-computer-mouse">:computer-mouse:</i> Click **Advanced Settings** to expand all available attack methods.

{% hint style="info" %}
All added attack methods are enabled by default except **Reverse DNS Lookup**. To disable a setting, deselect the checkbox <i class="fa-square-check">:square-check:</i> next to the corresponding setting. Select the checkbox <i class="fa-square">:square:</i> to enable it.
{% endhint %}

The following options are available:

<table><thead><tr><th width="240.00390625">Option</th><th>Description</th></tr></thead><tbody><tr><td>Run Bruteforce</td><td>Allow passwords to be tested automatically during the penetration test to assess access to user accounts and search for additional vulnerabilities as an authenticated user.</td></tr><tr><td>Include Default Password List for Bruteforce Attacks</td><td><p>Allow a predefined default password list to be tested during the penetration test in addition to the <a href="#own-password-list">custom password list</a>.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>The custom password list is prioritized during the assessment.</p></div></td></tr><tr><td>Run BSI Check</td><td>Allow SSL/TLS encryption to be assessed during the penetration test based on the BSI TR-03116-4 checklist.</td></tr><tr><td>Run UDP Based Default Discoveries (DNS, mDNS, SNMP)</td><td><p>Allow checks to be performed during the penetration test that are only possible using the User Datagram Protocol (UDP). This applies, for example, when assessing Domain Name System (DNS) server connections or using network protocols such as Multicast DNS (mDNS) or the Simple Network Management Protocol (SNMP).</p><div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p><strong>Please note</strong>: In rare cases, these checks can cause increased network load or even temporary unavailability.</p></div></td></tr><tr><td>Include Printers</td><td><p>Allow printers and scanners to be assessed for vulnerabilities during the penetration test.</p><div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p><strong>Please note</strong>: Enabling this option can cause configuration changes on the printer or unintended printouts.</p></div></td></tr><tr><td>Run Certificate Validation</td><td><p>Allow the validity of SSL/TLS certificates to be checked during the penetration test.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Please note</strong>: When scanning internal networks, certificate validation can generate warnings that do not necessarily require action in this context.</p></div></td></tr><tr><td>Execute Custom Scripts</td><td><p>Allow custom scripts stored on the selected Hacktor to be executed during the penetration test.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Please note</strong>: Enabling this option has no effect if no custom scripts are stored on the selected Hacktor.</p></div></td></tr><tr><td>Reverse DNS Lookup</td><td><p>Allow reverse DNS (rDNS) lookups to be performed during the penetration test to resolve IP addresses to host names.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Please note</strong>: In larger networks or when multiple host names are associated with one IP address, redundant scans can occur and increase the duration of the audit.</p></div></td></tr></tbody></table>

***

## Own Password List

{% hint style="danger" %}
We strongly recommend that you set up Field Level Encryption if you store custom password lists for running audits. If **Field Level Encryption is not configured**, stored passwords are **visible in plain text in reports**.
{% endhint %}

{% hint style="success" icon="lightbulb" %}
For more information on how to configure Field Level Encryption, see our Knowledge Base: [How do I set up Field Level Encryption in Enginsight?](https://docs.enginsight.com/docs/knowledge-base/english/configuration/how-do-i-set-up-field-level-encryption-in-enginsight)
{% endhint %}

Here you can add user accounts and passwords to the audit definition for use when simulating brute-force attacks during a penetration test.

<figure><img src="https://2423388680-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV7OrHgKXA0t1jankQBYf%2Fuploads%2FvKTWkqScpeBTkqC10JCi%2Fenginsight-screenshot-penetrations%20testing-management-audit%20definitions-add%20audit%20defintion-own%20password%20list.jpg?alt=media&amp;token=dfc44c51-fe7e-4f9e-8ff7-c42b4840b8cc" alt=""><figcaption></figcaption></figure>

<i class="fa-computer-mouse">:computer-mouse:</i> Click the **Own Password List** field to open the **Passwords** input field.

<i class="fa-pen">:pen:</i> Enter user names and their corresponding passwords in the **Passwords** field. The following syntax rules apply:

* Replace `<username>` completely with a user name. Omit the angle brackets.
* Replace `<password>` completely with a password. Omit the angle brackets.
* Use a colon `:` to separate the user name and password.

For example: `johndoe:myExamplePassword123!`

{% hint style="warning" %}
**Please note**: If you do not use a colon to separate the user name and password, the entire corresponding line is used as the password. In this case, the default user for the assessed service is used as the user name.
{% endhint %}

***

## Further Resources

**Knowledge Base**

* [How do I set up Field Level Encryption in Enginsight?](https://docs.enginsight.com/docs/knowledge-base/english/configuration/how-do-i-set-up-field-level-encryption-in-enginsight)

***
