> 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/basics/start-guide.md).
# Start Guide
You have just installed Enginsight or received access to the Enginsight SaaS platform and are ready to get started, but you're not sure where to begin.
This Start Guide provides a few recommendations to help you familiarize yourself with the Enginsight platform:
* [0 – Logging in to the Enginsight Platform](#id-0-logging-in-to-the-enginsight-platform)
* [1 – Configuring Initial Settings in the Enginsight Platform](#id-1-configuring-initial-settings-in-the-enginsight-platform)
* [2 – Setting Up Host Monitoring](#id-2-setting-up-host-monitoring)
* [3 – Setting Up Endpoint Monitoring](#id-3-setting-up-endpoint-monitoring)
* [4 – Creating an Inventory of Your Network](#id-4-creating-an-inventory-of-your-network)
* [5 – Setting Up Penetration Testing](#id-5-setting-up-penetration-testing)
* [6 – Configuring First Alerts](#id-6-configuring-your-first-alerts)
* [Advanced Topics](#advanced-topics)
***
## 0 – Logging in to the Enginsight Platform
{% stepper %}
{% step %}
### Sign in for the first time
If you have not already done so, sign in to the Enginsight user interface using the [temporary login credentials](/docs/manual/english/installation-and-configuration/installation-and-configuration/enginsight-platform/automated-installation/application-server.md#vorlaufige-login-daten-fur-die-benutzeroberflache) that are provided after the installation and setup of the Application Server.
If you have already signed in once, use the credentials for your user account to [log in](/docs/manual/english/basics/login.md).
{% endstep %}
{% step %}
### Familiarize yourself with the general layout
After signing in, the Home window of the Enginsight platform is shown. This corresponds to the view **Dashboard** → [Overview](/docs/manual/english/platform-usage/dashboard/overview.md).
Take some time to familiarize yourself with the [general layout](/docs/manual/english/basics/general-layout.md) of the user interface.
{% endstep %}
{% step %}
### Set up two-factor authentication
To improve the security of your Enginsight instance, you should configure [two-factor authentication](/docs/manual/english/installation-and-configuration/installation-and-configuration/additional-configurations/two-factor-authentication.md) if you have not already done so.
{% endstep %}
{% endstepper %}
***
## 1 – Configuring Initial Settings in the Enginsight Platform
{% stepper %}
{% step %}
### Complete your user account settings
:compass: Navigate to **Settings** → [User Account](/docs/manual/english/administration/settings/user-account.md) to review your user profile settings and adjust user-specific configurations.
* Complete [your personal information](/docs/manual/english/administration/settings/user-account.md#deine-personlichen-angaben) as needed. Make sure to enter the correct email address so that you can receive alert notifications and other platform messages. You should also configure the correct **Time Zone** for your user account, as this affects data that is shown throughout the platform, as well as reporting and alert detection.
* Change the [password](/docs/manual/english/administration/settings/user-account.md#passwort) for your user account if you have not already done so.
* Under [Advanced Settings](/docs/manual/english/administration/settings/user-account.md#erweiterte-einstellungen), enable **Two-Factor Authentication on Login** if you have not already done so.
{% endstep %}
{% step %}
### Complete your organization settings
:compass: Navigate to **Settings** → [Organisation](/docs/manual/english/administration/settings/organisation.md) to review your organization's settings and adjust organization-specific configurations.
* Complete your [organization details](/docs/manual/english/administration/settings/organisation.md#angaben-zur-organisation) as needed. In addition to the organization's address, configure the correct **Time Zone** for your organization.
* If you are using the SaaS version of Enginsight, also configure your [billing address](/docs/manual/english/administration/settings/organisation.md#rechnungsadresse).
* Under [Advanced Settings](/docs/manual/english/administration/settings/organisation.md#erweiterte-einstellungen), enable **Two-Factor Authentication for All Team Members** if you have not already done so.
For more information about organizations in Enginsight, see the chapter [Organization Management](/docs/manual/english/administration/organization-management.md).
{% endstep %}
{% step %}
### Invite first team members
:compass: Navigate to **Settings** → [Team Members](/docs/manual/english/administration/settings/team-members.md) to manage users within your organization and [add your first team members](/docs/manual/english/administration/settings/team-members/add-team-member.md).
{% hint style="info" icon="square-check" %}
We recommend that you assign the appropriate [system roles](/docs/manual/english/administration/permission-management.md#systemrollen) to new team members as soon as they are added.
{% endhint %}
{% endstep %}
{% step %}
### Add user groups
:compass: Navigate to **Settings** → [Groups](/docs/manual/english/administration/settings/groups.md) to [create new user groups](#benutzergruppen-erstellen).
{% hint style="info" icon="square-check" %}
We recommend that you organize team members into user groups. For example, this allows you to send alert notifications to groups instead of individual users. Groups are independent of the [permissions](/docs/manual/english/administration/permission-management.md) assigned to individual team members. Permissions are always defined through [roles](/docs/manual/english/administration/settings/roles.md).
{% endhint %}
{% endstep %}
{% endstepper %}
***
## 2 – Setting Up Host Monitoring
{% stepper %}
{% step %}
### Add your first hosts
In Enginsight, a **host** is a server or client on which the Enginsight agent **Pulsar** was installed to monitor the host from within.
:compass: Navigate to **Hosts** → **Overview** to add your first hosts.
* Add your first hosts by [installing the Enginsight agent Pulsar](/docs/manual/english/installation-and-configuration/installation-and-configuration/enginsight-components/pulsar.md) on them. Be sure to review the [system requirements for Pulsar](/docs/manual/english/installation-and-configuration/system-requirements/pulsar.md) beforehand.
* If you want to install Pulsar on multiple hosts at the same time, this is also possible.
{% hint style="success" icon="lightbulb" %}
For more information on how to roll out the Pulsar to multiple Windows systems, see our Knowledge Base:
* [How can I automatically roll out the Enginsight Pulsar to multiple persistent Windows systems?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-systems)
* [How can I automatically roll out the Enginsight Pulsar to volatile Windows VDI environments?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-volatile-windows-vdi-environments)
* [How can I manually roll out the Enginsight Pulsar to multiple persistent Windows VMs?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-manually-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-vms)
* [How can I roll out the Enginsight Pulsar via Windows Group Policy?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-roll-out-the-enginsight-pulsar-via-windows-group-policy)
{% endhint %}
{% endstep %}
{% step %}
### Add global tags
[Global tags](/docs/manual/english/platform-usage/hosts/management/global-tags.md) are custom tags that can be used across the entire Enginsight platform for groups of assets (hosts and endpoints). They help you apply settings to multiple assets at once or configure alerts for multiple assets simultaneously.
:compass: Navigate to **Hosts** → **Management** → **Global Tags** to [add new global tags](/docs/manual/english/platform-usage/hosts/management/global-tags/add-global-tag.md).
{% hint style="info" icon="square-check" %}
We recommend that you create tags for the operating systems used by your hosts, as well as tags for the detection levels of the [Intrusion Detection Systems (IDS)](/docs/manual/english/platform-usage/hosts/intrusion-detection-system.md) and the [Intrusion Prevention System (IPS) Shield](/docs/manual/english/platform-usage/shield.md).
{% endhint %}
{% endstep %}
{% step %}
### Add your first policy managers
Using [policy managers](/docs/manual/english/platform-usage/hosts/management/policy-manager.md), you can centrally define and manage settings for multiple hosts at once. These settings can then be automatically applied to newly added hosts through the use of tags.
:compass: Navigate to **Hosts** → **Management** → **Policy Manager** to [add a new policy manager](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md).
{% hint style="info" icon="square-check" %}
We recommend that you create the following policy managers first:
* A policy with the assigned tag **Server** and with the option [Advanced Settings](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#erweiterte-einstellungen) → **Recording of security relevant events** enabled. This option must be enabled before results can be shown under **Hosts** → **Management** → [System Events](/docs/manual/english/platform-usage/hosts/management/system-events.md).
* A policy with the assigned tag **IDS** (or a similar tag) and with the option [Enginsight Intrusion Detection System (IDS)](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#enginsight-intrusion-detection-system-ids) enabled using **Detection Level 2**. This option must be enabled before results can be shown under **Hosts** → **Intrusion Detection System** → [Network Anomalies](/docs/manual/english/platform-usage/hosts/intrusion-detection-system/network-anomalies.md).
* A policy with the assigned tag **IPS** or **Shield** (or a similar tag) and with the option [Enginsight Shield (IPS)](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#enginsight-shield-ips) enabled.
In general, we recommend that you add a separate policy manager for each Enginsight feature.
{% endhint %}
{% endstep %}
{% step %}
### Automatically block first network attacks
[Shield](/docs/manual/english/platform-usage/shield.md) is the Intrusion Prevention System (IPS) of Enginsight. With Shield, you can selectively block network traffic and attacks detected by the [Enginsight Intrusion Detection System (IDS)](/docs/manual/english/platform-usage/hosts/intrusion-detection-system.md) on all hosts that run Pulsar.
[Autopilots](/docs/manual/english/platform-usage/shield/dynamic-blocking/autopilot.md) are the automated Shield rules in the Enginsight platform.
:compass: Navigate to **Shield** → **Dynamic Blocking** → **Autopilot** to [add a new Autopilot](/docs/manual/english/platform-usage/shield/dynamic-blocking/autopilot/add-autopilot.md).
Assign hosts using the appropriate tags and set the [blocking level of the Intrusion Prevention System](/docs/manual/english/platform-usage/shield/dynamic-blocking/autopilot/add-autopilot.md#blockierungsgrad-des-intrusion-prevention-systems) to **Level 2: Balanced Availability and Security**.
{% hint style="warning" icon="square-check" %}
We strongly recommend that you introduce Shield rules step by step and monitor the available performance resources of the Application Server. Depending on how many network anomalies are detected and blocked, Shield can significantly increase CPU and memory utilization on the Application Server.
{% endhint %}
{% endstep %}
{% endstepper %}
***
## 3 – Setting Up Endpoint Monitoring
In Enginsight, an [endpoint](/docs/manual/english/platform-usage/endpoints.md) is an internal or external website or domain that is monitored from different (geographic) locations using the Enginsight component **Observer**.
This includes checking the validity of SSL/TLS certificates, scanning for vulnerabilities and malware, verifying compliance with specific security policies, and monitoring availability and performance.
{% stepper %}
{% step %}
### Install your first Observers
To monitor an endpoint, you must [install at least one Observer](/docs/manual/english/installation-and-configuration/installation-and-configuration/enginsight-components/observer.md). You can also install multiple Observers to monitor an endpoint from different locations or regions. Be sure to review the [system requirements for Observer](/docs/manual/english/installation-and-configuration/system-requirements/komponentenserver-hacktor-watchdog-observer.md#zusatzliche-anforderungen-observer) beforehand.
:compass: Navigate to **Endpoints** → **Required Services** → [Observers](/docs/manual/english/platform-usage/endpoints/required-services/observer.md) to add a new Observer.
{% hint style="info" icon="square-check" %}
We recommend that you enter the **Region** of an Observer so that it reflects either the network location (for example, **Internal**) or the actual region (for example, **EU-Central**).
We also recommend that you always enable *both* options **Operate as a Dedicated Observer** and **Allow Internal Targets**.
{% endhint %}
{% endstep %}
{% step %}
### Add your first endpoints
:compass: Navigate to **Endpoints** → **Overview** to [add a new endpoint](/docs/manual/english/platform-usage/endpoints/overview/add-endpoint.md).
When you enter the **URL** that you want to scan, make sure to specify whether the endpoint uses http\:// or https\://.
{% hint style="info" icon="square-check" %}
We recommend that you always enter URLs in the following format: ****.
{% endhint %}
{% endstep %}
{% endstepper %}
***
## 4 – Creating an Inventory of Your Network
In Enginsight, the agentless inventory of all network devices within an organization's IT infrastructure is referred to as **Discovery**. [Discoveries](/docs/manual/english/platform-usage/discoveries.md) are performed using the Enginsight component **Watchdog**.
{% stepper %}
{% step %}
### Install your first Watchdogs
To create an inventory of your network, you must [install at least one Watchdog within a subnet](/docs/manual/english/installation-and-configuration/installation-and-configuration/enginsight-components/watchdog.md). Be sure to review the [system requirements for Watchdog](/docs/manual/english/installation-and-configuration/system-requirements/komponentenserver-hacktor-watchdog-observer.md#zusatzliche-anforderungen-watchdog) beforehand.
:compass: Navigate to **Discoveries** → **Required Services** → [Watchdogs](/docs/manual/english/platform-usage/discoveries/required-services/watchdogs.md) to add a new Watchdog.
Enter a meaningful name for your Watchdog, [define a subnet using CIDR notation](/docs/manual/english/appendix/defining-ip-address-ranges-and-subnets.md), and enable the option **Permanent Monitoring** to begin the inventory process.
{% hint style="warning" icon="square-check" %}
We strongly recommend that you **not reduce** the scanning interval that is predefined in the **Active Network Scan after (Minutes)** field for the initial scan. Active network scans generate significant network traffic and can quickly overload a system.
{% endhint %}
{% endstep %}
{% step %}
### Review the inventory
:compass: Navigate to **Discoveries** → [Inventory](/docs/manual/english/platform-usage/discoveries/inventory.md) to view and check all discovered network devices.
{% endstep %}
{% endstepper %}
***
## 5 – Setting up Penetration Testing
A [penetration test](/docs/manual/english/platform-usage/penetration-testing.md) is a planned and controlled automated attack against your own systems to identify vulnerabilities. Penetration tests are performed using the Enginsight component **Hacktor**.
You can perform penetration tests against hosts running Pulsar, against entire subnets, or against systems that are already monitored by a Watchdog.
{% stepper %}
{% step %}
### Install your first Hacktors
To perform penetration testing, you must [install at least one Hacktor in the subnet](/docs/manual/english/installation-and-configuration/installation-and-configuration/enginsight-components/hacktor.md) you want to audit. Be sure to review the [system requirements for Hacktor](/docs/manual/english/installation-and-configuration/system-requirements/komponentenserver-hacktor-watchdog-observer.md#system-requirements-component-server) beforehand.
:compass: Navigate to **Penetration Testing** → **Required Services** → [Hacktors](/docs/manual/english/platform-usage/penetration-testing/required-services/hacktors.md) to add a new Hacktor.
{% hint style="info" icon="square-check" %}
We recommend that you leave the default Hacktor settings unchanged or even set the option **Frequency** to **Low**. While this increases the overall duration of a penetration test, it can help prevent resource exhaustion if insufficient system resources are available.
{% endhint %}
{% endstep %}
{% step %}
### Define your first target systems
A [target group](/docs/manual/english/platform-usage/penetration-testing/management/target-groups.md) allows you to group systems that should be included in a penetration test. Targets can be defined using IP addresses, hostnames, IP address ranges, subnets, Watchdogs, or endpoints.
:compass: Navigate to **Penetration Tests** → **Management** → **Target Groups** to add a [new target group](/docs/manual/english/platform-usage/penetration-testing/management/target-groups/add-target-group.md).
{% hint style="warning" icon="square-check" %}
We recommend that you define **no more than 1,000 IP addresses** per audit.
We also recommend that you evaluate whether it would be more efficient to use the **asset inventory of a Watchdog** as the basis for penetration testing.
Since Hacktor pings every individual IP address, penetration tests that cover an entire subnet take significantly longer. In addition, results will often include many offline targets because, in most environments, only a small portion of a subnet is actively used.
Please also note that you should define either an IP address range **or** a Watchdog to avoid duplicate scan results.
{% endhint %}
{% endstep %}
{% step %}
### Create your first audit templates
[Audit definitions](/docs/manual/english/platform-usage/penetration-testing/management/audit-definitions.md) allow you to create reusable templates for penetration tests and ensure comparable results across multiple audit runs.
:compass: Navigate to **Penetration Testing** → **Management** → **Audit Definitions** to [add a new audit template](/docs/manual/english/platform-usage/penetration-testing/management/audit-definitions/add-audit-definition.md).
Enter a meaningful name for the template, select the target system to be scanned, and define the Hacktor that should perform the penetration test.
{% hint style="warning" icon="square-check" %}
We strongly recommend that you **not define recurring execution yet**. Instead, closely monitor the penetration test that is performed using the audit template you created.
Running penetration tests during an audit may **affect the availability of your systems**, depending on how many IP addresses are scanned by the Hacktor.
Also note that, depending on the stability of your IT infrastructure, a **complete system outage can never be ruled out entirely** when running a penetration test.
{% endhint %}
{% endstep %}
{% step %}
### Start a penetration test
You can now start your first [penetration test audit](/docs/manual/english/platform-usage/penetration-testing/management/audit-definitions.md#penetrationstest-audit-starten).
All completed audits can be found under **Penetration Tests** → [Audits](/docs/manual/english/platform-usage/penetration-testing/audits.md). Click an audit to open its [detail view](/docs/manual/english/platform-usage/penetration-testing/audits/audit-detail-views.md), where you can review all results and analyses generated during the penetration test.
{% hint style="info" icon="square-check" %}
As a general rule, we recommend that you initially run penetration tests against **no more than one to three non-critical targets** to check the configuration and behavior of Hacktor within your environment.
With only a small number of targets, detailed results are typically available within 5-10 minutes, which allows you to understand how Hacktor works without unnecessarily affecting system performance or availability.
{% endhint %}
{% endstep %}
{% endstepper %}
***
## 6 – Configuring First Alerts
You can now configure your first [alerts](/docs/manual/english/platform-usage/alerts.md) to receive notifications whenever Enginsight detects a security-relevant issue or incident.
:compass: Navigate to **Alerts** → [Overview](/docs/manual/english/platform-usage/alerts/overview.md) to [add a new alert](/docs/manual/english/platform-usage/alerts/overview/add-alert.md).
{% stepper %}
{% step %}
### Alerts for hosts
For hosts, we recommend that you configure the following alerts right away:
* **Failed Login Attempt**: Triggers an alert whenever a user fails to log in to a system (Windows Event ID 4625).
* **New Admin Account Created (only Windows)**: Triggers an alert whenever a new administrator account is created (Windows-Event 4720).
* **New User Account Created (only Windows)**: Triggers an alert whenever a new user account is created (Windows-Events 4720, 4732, 4728).
* **Suspicious Network Traffic**: Triggers an alert whenever the IDS detects a potential network attack. We recommend that you set the severity threshold to **High**.
* **Installed/Uninstalled Software**: Triggers an alert whenever software is installed on or removed from a host.
* **New Open Port**: Triggers an alert whenever a new open port is detected on a host. We recommend that you assign hosts using the **Server** tag.
* **New Vulnerabilities (CVSS Score)**: Triggers an alert whenever the CVSS score of a vulnerability on a host reaches a defined threshold. We recommend that you use a threshold value of **7**.
{% endstep %}
{% step %}
### Alerts for endpoints
For endpoints, we recommend that you configure the following alerts right away:
* **Website not Available**: Triggers an alert whenever an endpoint can no longer be reached or loaded.
* **New Vulnerability**: Triggers an alert whenever a new vulnerability (CVE) is identified on an endpoint.
* **DNS Record Changed**: Triggers an alert whenever records in the Domain Name System (DNS) are modified.
* **Data Protection**: Triggers an alert whenever the SSL/TLS configuration of an endpoint does not comply with the requirements defined by the German Federal Office for Information Security (BSI).
* **Days Until Certificate Expires**: Triggers an alert whenever the expiration date of an SSL/TLS certificate falls below a defined threshold.
{% endstep %}
{% endstepper %}
***
## Advanced Topics
Once you have become familiar with the core functionality of Enginsight, we recommend exploring the following topics:
{% stepper %}
{% step %}
### Define additional policy managers
* Enable [automatic operating system and feature updates](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#automatische-os-updates) on assigned hosts to ensure that you do not miss important security updates.
* Enable the [use of plugins](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#plugins) on assigned hosts, allowing custom scripts to be executed in response to alerts or other events.
* Use the [File Integrity Monitoring (FIM) feature](/docs/manual/english/platform-usage/hosts/file-integrity-monitoring.md) to monitor the integrity of files and directories. Enable [File Integrity Monitoring](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#file-integrity-monitoring) with a policy manager and create your first [FIM rule set](/docs/manual/english/platform-usage/hosts/file-integrity-monitoring/rules/add-rule.md).
* Use the [Advanced Persistent Threats (APT) feature](/docs/manual/english/platform-usage/hosts/advanced-persistent-threats.md) to scan your systems for advanced threats. Enable [APT scanning](/docs/manual/english/platform-usage/hosts/management/policy-manager/add-policy-manager.md#advanced-persistent-threats) with a policy manager, add your first [APT rule sets](/docs/manual/english/platform-usage/hosts/advanced-persistent-threats/rules.md) (maintained by Enginsight), and define recurring scanning [plans](/docs/manual/english/platform-usage/hosts/advanced-persistent-threats/plans.md).
{% endstep %}
{% step %}
### Extend your audit definitions for penetration tests
* Enter [custom password lists](/docs/manual/english/platform-usage/penetration-testing/management/audit-definitions/add-audit-definition.md#eigene-passwortliste) in audit definitions that can be used during penetration tests to simulate brute-force attacks. This is useful, for example, when checking the network for outdated local user accounts.
* Add [authentication providers](/docs/manual/english/platform-usage/penetration-testing/management/auth-providers.md) to store credentials for target systems and retrieve additional information such as operating system details and installed software. This allows Hacktor to identify and validate more vulnerabilities than would be possible using only publicly accessible information.
* Create custom scripts that Hacktor can use during penetration tests.
{% hint style="success" icon="lightbulb" %}
For more information on how to use custom scripts with Hacktor, see our Knowledge Base: [How can I use custom scripts in penetration tests with Enginsight?](https://docs.enginsight.com/docs/knowledge-base/english/penetration-tests/how-can-i-use-custom-scripts-in-penetration-tests-with-enginsight)
{% endhint %}
{% endstep %}
{% step %}
### Add further alerts
* Create additional alerts for your hosts and endpoints.
* Create and configure [webhooks](/docs/manual/english/platform-usage/alerts-beta/webhooks-beta.md) that integrate alerts with third-party software so that notifications can also be delivered outside the Enginsight platform.
* Configure SMS notifications to receive alert notifications directly on your mobile phone.
{% hint style="success" icon="lightbulb" %}
For more information on how to configure SMS notifications in Enginsight, see our Knowledge Base: [How do I configure SMS notifications for alerts in Enginsight?](https://docs.enginsight.com/docs/knowledge-base/english/alerting/how-do-i-configure-sms-notifications-for-alerts-in-enginsight)
{% endhint %}
{% endstep %}
{% endstepper %}
***
## Further Resources
**Knowledge Base**
* [How can I automatically roll out the Enginsight Pulsar to multiple persistent Windows systems?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-systems)
* [How can I automatically roll out the Enginsight Pulsar to volatile Windows VDI environments?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-automatically-roll-out-the-enginsight-pulsar-to-volatile-windows-vdi-environments)
* [How can I manually roll out the Enginsight Pulsar to multiple persistent Windows VMs?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-manually-roll-out-the-enginsight-pulsar-to-multiple-persistent-windows-vms)
* [How can I roll out the Enginsight Pulsar via Windows Group Policy?](https://docs.enginsight.com/docs/knowledge-base/english/pulsar/how-can-i-roll-out-the-enginsight-pulsar-via-windows-group-policy)
* [How can I use custom scripts in penetration tests with Enginsight?](https://docs.enginsight.com/docs/knowledge-base/english/penetration-tests/how-can-i-use-custom-scripts-in-penetration-tests-with-enginsight)
* [How do I configure SMS notifications for alerts in Enginsight?](https://docs.enginsight.com/docs/knowledge-base/english/alerting/how-do-i-configure-sms-notifications-for-alerts-in-enginsight)
***