Audit Definitions
Last updated
Last updated
Templates help you with standardized penetration tests. This allows you to ensure the reproducibility and comparability of repetitive pentests. You can use a template to define which hacking gate should attack which target systems. You can also define further specifications.
To add a new audit definition, click on the corresponding button. Configure your definition according to the following options.
Assign a meaningful name and a description. Select a hacktor that is to attack the selected target systems. Specify the target systems that Hacktor should attack. You can add both a single target system and multiple target systems to the template. If you have stored access data for target systems that you want to use for the pentest, select your auth providers.
The host on which Hacktor is installed must be able to communicate with the target systems. If necessary, check your firewall settings and add Hacktor to an IDS whitelist.
The "Recurring execution" option allows you to schedule future executions. You can choose to repeat an execution on a certain day of the week (Daily), a certain day of the month (Monthly) or to work with a cronjob (Custom).
Audits can be started a maximum of once every 3 hours using the "Scheduled execution" option.
Not yet available in the current beta version!
If you have activated recurring execution, you have the option of automatically sending the audit report as a PDF to team members by email. Select one or more members and assign a password with which the audit report is to be encrypted.
It is also possible to send the audit reports unencrypted. However, we strongly recommend that you make use of the encryption option.
In the advanced settings, you can activate and deactivate certain types of attacks to customize the pentest to your needs. If penetration tests lead to problems in the regular operation of your IT (e.g. overload, printer prints error pages, etc.), you can often resolve the problem with the advanced settings. You have the following options:
Run Bruteforce Automatically try passwords for the following services.
Include default password list for bruteforce attacks Use the Enginsight password list or only use your own password list.
Run BSI check Check SSL/TLS encryption SSL/TLS encryption based on BSI checklist TR-03116-4.
Run UDP based default discovery (DNS, mDNS, SNMP) Checks that work by default or exclusively via UDP. In rare cases, this can lead to a high network load or unavailability, among other things.
Include printers A penetration test on a printer can lead to configuration changes or unintentional printing.
Run certificate validation When scanning internal networks, certificate validation potentially leads to warnings that are irrelevant in this case.
Execute custom scripts Execute or ignore custom scripts defined in the hack gate.
Enter your own password list here. Please note the following syntax:
<username>:<password>
Separate the username and password with a colon. If there is no colon, the entry is used as the password and the default user of the respective service is used as the user.
