4.1. License Management¶
Login to ASGARD, navigate to
Upload ASGARD Management Center License and upload a valid license.
After uploading, the license details are displayed.
4.2. System Status¶
4.2.1. Status Overview¶
The initial system status page provides a summary of the most important system components.
It also includes the current resource consumption (disk, CPU and memory) and lists the currently installed ASGARD software version along with available versions of THOR. Additionally, the connection status to the update servers, MASTER ASGARD and Cockpit are shown with a graph that shows asset connections and asset streams.
The THOR version numbers may be missing in a new installation. THOR is not included in the installed packages. THOR is downloaded automatically after the installation and should show up not later than one hour after installation.
The diagnostics sub menu shows the periodically performed checks and their status. Clicking the magnifying glass icon shows details of the performed check. If a check failed it gives a detailed error message and hints on which steps typically help in resolving the issue.
The traffic light on the left menu always shows if any of those checks failed by showing a warning or error (i.e. yellow or red light) and you can click the status to view the diagnostics page as a pop-up.
The logs section shows the latest and most relevant logs. Complete logs can be found at
Available logs and their content:
- Audit: Containing user login/-off, changes done over the UI.
- ASGARD Management Center: Overall status of the MC, general errors and warnings.
- ASGARD Agent and Service Controller: Status of the agents deployed on assets.
- THOR via Syslog: Received syslog events of THOR scans. Partial results if a scan did not complete.
- Aurora: All Aurora events:
- Aurora Event Producers: The top 10 of event producing processes per endpoint.
- Aurora Response Actions: Only response action events of Aurora:
- Aurora Simulated Response Actions: Only simulated response action events of Aurora.
- LogWatcher: All LogWatcher events.
- Diagnostic Pack: Button for generating and downloading a diagnostic pack that may be asked for by support.
4.3. ASGARD Agent Deployment¶
In order to register a new endpoint to the ASGARD Management Center, download and install the ASGARD agent on the system you want to register.
The ASGARD agent can be directly downloaded from the ASGARD login screen through the button
Download Agent Installers. A list of available agents for various operating systems appears.
After installation, the endpoints will connect to ASGARD, register automatically and appear in the Asset Management Section in the tab
Requests. Please allow two or three minutes for systems to show up. The agents use the hostname to connect to ASGARD, ensure that your endpoints can resolve and reach the ASGARD hostname.
In the requests tab, select the agents you want ASGARD to manage and click
Accept. After that, the endpoint shows up in the asset tab and is now ready to be managed or scanned.
A registered agent will poll to the ASGARD Management Center at a given interval between 10 seconds and 600 seconds – depending on the number of connected endpoints (see section Performance Tuning for details). If ASGARD has scheduled a task for the endpoint (for example: run THOR scan) it will be executed directly after the poll.
4.4. Asset Management¶
4.4.1. Asset Overview¶
Management of all endpoints registered with ASGARD can be performed in Asset Management. The assets will be presented as a table with an individual ASGARD ID, their IP addresses and host names.
By clicking the control buttons in the Actions column, you can start a new scan, run a response playbook, open a command line or switch the endpoints ping rate to a few seconds instead of a maximum of 10 minutes.
- The internal ping between the ASGARD agent and ASGARD is based on HTTPS not ICMP
- Depending on the user's role some of the control buttons may be disabled
4.4.2. Column Visibility¶
Users can select various columns and adjust their view according to their needs by clicking the gear wheel in the top right corner of any table.
4.4.3. Asset Labels¶
Labels are used to group assets. These groups can then be used in scans or tasks.
You can add multiple labels to an asset or a group of assets. This is done by selecting the particular assets in the left column, typing the label name (e.g. New_Label) and clicking the blue
Add Labels button.
Don't use labels with white space characters as it could cause issues in syncs with Analysis Cockpit, exports / imports or other underlying legacy functions.
In order to remove labels, select your assets, click the yellow
Remove Labels button and type the name of the label you want to remove for these assets.
The asset management section has extensive filtering capabilities, e.g. it is easy to select only Linux endpoints that have been online today and have a particular label assigned.
184.108.40.206. Export Asset List¶
The Import/Export Section allows you to export your assets to a .csv file.
220.127.116.11. Import Labels¶
The import function allows you to add or remove labels on assets based on columns in that CSV file.
The import function processes the values in the columns
Add Labels ... and
Remove Labels ... only. In order to change labels, use the already exported list, add values in these columns and re-import it by using the
Apply Labels from CSV button. Separate multiple labels with comma. Leading or ending white space characters will be stripped from the labels.
4.5. Scan Control¶
4.5.1. Managing Scan Templates¶
Scan templates are the most convenient way to make use of THOR's rich set of scan options. Starting with ASGARD 1.10., it is possible to define scan parameters for THOR 10 and store them in different templates for later use in single scans and grouped scans.
Imagine you want to use dedicated scan options for different system groups (e.g. Linux Servers, Domain Controllers, Workstations, etc.) and make sure to use exactly the same set of scan options every time you scan a particular group of systems. With ASGARD you can now add a scan template for every group.
A popular use case for scan templates is providing additional resource control – for example telling THOR to set the lowest process priority for itself and never use more than 50% of CPU.
Please keep in mind, that we have already optimized THOR to use the most relevant scan options for a particular system (based on type, numbers of CPUs and system resources) and a comprehensive resource control is enabled by default.
For more details please refer to the THOR manual. Only use the scan templates if you want to deviate from the default for a reason.
Scan templates are protected from being modified by ASGARD users without the "Manage Scan Templates"-permission and can also be restricted from being used by ASGARD users in case the flag "ForceStandardArgs" is set for this user. (See section User Management for details).
By clicking the
Import Scan Template button you can import a previously exported scan template.
In order to create a scan template, navigate to
Scan Control >
Scan Templates and click the
Add Scan Template button. The
Add Scan Template dialogue appears. The current THOR scanner version is chosen for you by default but can be changed if needed.
After choosing or changing a scanner you will find the most frequently used options on the top of this page in the "Favorite Flags" category. View all THOR options by clicking on the other categories or quickly search for known flags in the search bar. By clicking on the star symbols you can also edit your personal favorites.
By checking the "Default" box, you can make this scan template the default template for every new scan. There can only be one default template at a time and selecting the box will uncheck a previous default, if set. Checking the "Restricted" flag will make the template restricted, meaning only a restricted set of users can use the template for scans. The set of users consists of all users who do not have the "ForceStandardArgs" restriction set. (By default this are all users who are not member of the group "Operator Level 1"). After clicking the "Add Template" button on the bottom of the template page, an overview of all existing scan templates is shown.
4.5.2. Scan a Single System¶
18.104.22.168. Create a Single Scan¶
The creation of a scan is performed within the Asset Management. There is a button for each asset to create a new scan and to show all past scans.
Just click on the "THOR" button in the Action column in the Asset Management view.
Within this form, you can choose the maximum runtime, module, scanner, scan flags, signatures and template can be selected.
After the desired parameters have been set, the scan can be started by clicking the
Add Scan button.
22.214.171.124. Stopping a Single Scan¶
To stop a single scan, navigate to the "Single Scans" tab in Scan Control section and click the "stop" (square) button for the scan you want to stop.
126.96.36.199. Download Scan Results¶
After the scan completion, you can download the scan results via the download button in the actions column.
The download button has the following options:
- Download Scan Result as TXT (the THOR text log file)
- Download Scan Result as JSON (only available if it was started with the
- Download HTML Report (as *.gz compressed file; available for successful scans only)
- Show HTML Report (opens another tab with the HTML report)
4.5.3. Scan Groups of Systems¶
188.8.131.52. Create Grouped Scans¶
A scan for a group of systems can be created in the "Scan Control > Group Scans" tab. Click the
Add Group Scan button in the upper right corner.
As with the single scans, various parameters can be set. Aside from the already mentioned parameters, the following parameters can be set:
Freely selectable name for the group scan.
Here you can define which assets will be affected by the group scan. In case more than one label is chosen: An asset must have at least one chosen label attached to it to be affected by the scan. If no label is selected, all known assets will be scanned.
ASGARD will not send additional scans to the agents when the client limit is reached. Therefore you need to set a limit higher than the number of hosts you want to scan or enter
0 for no limit. If you are using MASTER ASGARD, this limit is applied on each single selected ASGARD.
The number of scans per minute that are issued by ASGARD. This is where the network load can be controlled. Additionally, it is recommended to use this parameter in virtualized and oversubscribed environments in order to limit the number of parallel scans on your endpoints.
After this time frame, no scan orders will be issued to the connected agents.
Select a date for a scheduled start of the scan.
After the group scan has been saved or saved and started, you will automatically be forwarded to the list of grouped scans.
184.108.40.206. List of all Group Scans¶
The list of all group scans contains, among other items, the unique Scan-ID and the name.
In addition, information can be found about the chosen scanner, the chosen parameters, the start and completion times and the affected assets (defined by labels). Additional columns can be added by clicking on "Column Visibility".
The Status field can have the following values:
Paused: The group scan has not yet started. Either click play or wait for the scheduled start date (the job will start in a 5 minute window around the scheduled time).
Active: Scan is started, ASGARD will issue scans with the given parameters.
Inactive: No additional scan jobs are being issued. All single scans that are currently running will continue to do so.
Completed: The group scan is completed. No further scan jobs will be issued.
220.127.116.11. Starting a Group Scan¶
A group scan can be started by clicking on the "play" button in the "Actions" column of a group scan. Subsequently, the scan will be listed as "Started".
18.104.22.168. Starting a Scheduled Group Scan¶
The Scheduled Group Scan section shows all scans that are to run on a frequent basis along with their periodicity. All group scans that have been started through the scheduler will show up on top of the Group Scan section the moment they are started. New scheduled tasks can be created by clicking the
Add Scheduled Group Scan button.
22.214.171.124. Details of a Group Scan¶
Further information about a group scan can be observed from the detail page of the group scan. Click the scan you are interested in and the details section will appear.
Aside from information about the group scan in the "Details" tab, there is a graph that shows the number of assets started and how many assets have already completed the scan in the "Charts" tab. In the "Tasks" tab you get information about the scanned assets.
4.5.4. THOR Excludes and False-Positive Filters¶
Be careful not to use too broad filters or excludes as this might cripple THOR's detection capabilities, if done incorrectly.
4.6. Response Control¶
4.6.1. Opening a Remote Shell on an endpoint¶
In order to open a remote shell on an endpoint, open the Asset Management section and click the "command line" button in the Actions column.
Depending on your configuration it may take between 10 seconds and 10 minutes for the remote shell to open. Please note that all actions within the remote shell are recorded and can be audited. All shells open with root or system privileges.
In order to replay a remote console session, navigate to
Response Control, expand the task that represents your session, select the
Console Log tab and click the play button in the bottom row.
ASGARD users can only see their own remote shell session. Only users with the
RemoteConsoleProtocol permission are able to replay all sessions from all users.
4.6.2. Response Control with Pre-Defined Playbooks¶
In addition to controlling THOR scans, ASGARD Management Center contains extensive response functions. Through ASGARD, you can start or stop processes, modify and delete files or registry entries, quarantine endpoints, collect triage packages and execute literally any command on connected systems. All with one click and executed on one endpoint or groups of endpoints.
It is also possible to download specific suspicious files. You can transfer a suspicious file to the ASGARD Management Center and analyze it in a Sandbox.
To execute a predefined response action on a single endpoint, navigate to the Asset Management view and click the "play" button in the Actions Column. This will lead you to a dialogue where you can select the desired action.
In this example, we collect a full triage package.
ASGARD ships with pre-defined playbooks for the following tasks:
- Collect full triage pack (Windows only)
- Isolate endpoint (Windows only)
- Collect system memory
- Collect file / directory
- Collect directory
- Collect Aurora diagnostics pack
- Execute command and collect stdout and stderr
Nextron provides additional playbooks via ASGARD updates.
The collection of memory can set the systems under high load and impacts the systems response times during the transmission of collected files. Consider all settings carefully! Also be aware that memory dumps may fail due to kernel incompatibilities or conflicting security mechanisms. Memory dumps have been successfully tested on all supported Windows operating systems with various patch levels. The memory collection on Linux systems depends on kernel settings and loaded modules, thus we cannot guarantee a successful collection. Additionally, memory dumps require temporary free disk space on the system drive and consume a significant amount of disk space on ASGARD as well. The ASGARD agent checks if there is enough memory on the system drive and adds a 50% safety buffer. If there is not enough free disk space, the memory dump will fail.
4.6.3. Response Control for Groups of Systems¶
Response functions for groups of systems can be defined in the
Group Tasks tab or the
New Scheduled Group Task tab.
4.6.4. Response Control with Custom Playbooks¶
You can add your own custom playbook by clicking the
Add Playbook button in the
Response Control >
This lets you define a name and a description for your playbook. After clicking the
Add Playbook button,
click on the
Edit steps of this playbook action.
This opens the side pane in which single playbook steps
can be added using the
Add Step button.
If you need custom files for your playbook (scripts, configurations, binaries, etc.) you can select local files to be uploaded to ASGARD during the creation of the playbook step (by selecting "Upload New File" in the file drop-down). You can manage these files at
Response Control >
Playbook Files and upload or update files using the
Upload Playbook File button.
You can have up to 16 steps in each playbook that are executed sequentially. Every step can be either "download something from ASGARD to the endpoint", "execute a command line" or "upload something from the endpoint to ASGARD". If you run a command line the stdout and stderr are reported back to ASGARD.
4.7. Service Control¶
Service Control is ASGARD's way of deploying real-time services on endpoints. Currently there exist the Aurora and the LogWatcher service. To use any of those two, the service controller has to be installed on an asset.
4.7.1. Service Controller Installation¶
To install asgard2-service-controller on an asset you need to install the asgard2-agent first. If you already have installed asgard2-agent on an asset and accepted it in ASGARD, you can use the "Install ASGARD Service Controller" playbook to deploy the service controller on an asset or you can manually download and execute the asgard2-service-controller installer from the ASGARD downloads page.
4.7.2. Service Controller Update¶
If an ASGARD update comes with a new service controller version, you need to update the service controller on the already rolled-out assets. You can do this using an "Update Agent" task. For a single asset the task can be run in
Asset Management >
Run Task (play button action) or analogous as a (scheduled) group task under
Response Control >
(Scheduled) Group Tasks >
Add (Scheduled) Group Task.
If you don't see the Update Agent module, you need to enable Show Advanced Tasks in
LogWatcher, as well as Aurora, are using Sigma in order to define their detections. The Sigma rule management is shared between the two services. But each service has its own configuration that defines which rules are actually used on the assets.
126.96.36.199. What is Sigma¶
From the project website:
Sigma is a generic and open signature format that allows you to describe relevant log events in a straightforward manner. The rule format is very flexible, easy to write and applicable to any type of log file. The main purpose of this project is to provide a structured form in which researchers or analysts can describe their once developed detection methods and make them shareable with others.
188.8.131.52. Creating a Ruleset¶
Rulesets are used to group rules to manageable units. As an asset can only have one service configuration, rulesets are used to determine which rules are used in which service configuration. There exist default rulesets for high and critical Sigma rules. If you want to create a custom ruleset go to
Service Control >
If you have chosen that new Sigma rules should be added automatically they are added now. If you didn't you now need to add the desired rules manually by going to
Service Control >
Rules. Choose the rules that should be added to this ruleset by selecting the checkboxes and then
Add to Ruleset. A rule can be assigned to multiple rulesets.
You need to commit and push your changes after editing a ruleset. ASGARD has to restart the service controller to read new configurations. In order to prevent multiple restarts in the case of a user performing several configuration changes in succession, the user has to initiate the reloading of the new configuration by going to
Service Control >
Rulesets and performing the Compile ruleset action (gear wheels). The need for compiling is indicated in the Uncompiled Changes column.
184.108.40.206. Choosing which Rules to activate¶
It is not advised to enable all available rules on an asset. We suggest to start with all "critical" and then advance to all "high" rules. We already provide a default ruleset for those two levels for you to use. "Medium" rules should not be enabled in bulk or "low"/"informational" at all . Single medium rules, which increase an organisation's detection coverage and do not trigger a bigger number of false positives can be added to the active configuration, but should be tested rule by rule.
In order to easily add rules to a ruleset you can use the column filters to select the desired rules and add the bulk to a ruleset. As an example you can add all rules of level "critical" to a ruleset:
Another great way to pivot the Sigma rule database is the usage of MITRE ATT&CK® IDs.
Or you can just search the title or description field of the rules. You can also search the rule itself using the "Rule" column. (the "Rule" column is not shown by default and has to be added using the gear wheel button).
220.127.116.11. False Positive Tuning of Sigma Rules¶
Not every environment is the same. It is expected that some rules will trigger false positive matches in your environment. You have multiple options to tackle that issue.
If it is a general false positive, probably not only occurring in your environment, consider reporting it at as a Github issue or e-mail to us (firstname.lastname@example.org). We will take care of the tuning for you and your peers.
If the false positive is specific to your environment you can tune single Sigma rules at
Rules, filter for the rule in question and choose the "Edit false positive filters of this rule" action. Here you can do simple rule tunings on your own. By clicking the "Add False Positive Filter" button you can add single lines that filter the event for false positives (i.e. they are OR-connected meaning: "Do not match the event if any of those lines matches). They are applied on top of the rule logic and persist automatic rule updates.
To see the resulting rule you can click the "Show Preview" button or look at the "Compiled Rule" row in the rule's drop down menu.
If you want to review the tuned rules: To filter for all rules containing a custom false positive tuning, you have to add the "Filters" column to your view (gear wheels icon) and show all non-empty rows by using the
NOT -column filter.
If the rule is adding too much noise and tuning is not sensible, you can remove the rule from the ruleset for a subset of your machines (maybe you need to define and use a separate ruleset for that use-case) or you can disable the rule altogether. This is done using the "Disable this rule" action of the rule. Disabling the rule affects the rule in all rulesets.
After tuning a rule, the rulesets using that rule have to be re-compiled at
Service Control >
18.104.22.168. Adding Custom Rules¶
Custom rules can be added using the sigma format complying with the specification. You can upload single files or a ZIP compressed archive. This can be done at
Service Control >
22.214.171.124. Rule and Response Updates¶
If new rules or rule updates are provides by the Aurora signatures, the updates have to be applied by the user manually in order to be affecting Aurora agents managed by ASGARD. An indicator is shown in the WebUI and the rules changes can be reviewed and applied at
Service Control >
Clicking on the
Update button in the "Update Available" column opens a diff view in which the changes are shown and where the user can apply or discard the changes. If you do not need to review each single change, you can apply all changes using the
Update All Rules button.
Analogous the updates of response actions can be viewed and applied at
Service Control >
126.96.36.199. How to activate Responses¶
As a fail safe and for administration purposes, responses are generally only simulated if not explicitly set to active. This has to be done on different levels:
- Service configuration level
- Ruleset configuration level (on updates)
- Ruleset rule level
If on one level a rule is simulated, it will not execute the response actions but only generate a log line that describes the action that would have been performed. You can see an overview of the state of all responses in the
Service Control >
- indicates whether responses are activated on configuration level. Edit the configuration to change it.
- indicates how many rules are only simulated in that ruleset (or in sum).
- indicates how many rules have active responses in that ruleset (or in sum)
To change the status of a response in the ruleset click the ruleset link. You can view all simulated or all active responses. Use the checkbox and the button in the upper right to switch the response status of the rules between active and simulated.
In addition the default response mode of a ruleset is important for the behaviour of response updates. It can be seen at
Service Control >
Rulesets in the "Default Response Mode" column.
If "Simulation" is selected, response actions of new and updated rules will be put in simulation mode. If "Active" is selected, new rules will automatically be put in active mode and updated rules will not change their current response mode.
- Aurora is a lightweight endpoint agent that applies Sigma rules and IOCs on local event streams.
- It uses Event Tracing for Windows (ETW) to subscribe to certain event channels.
- It extends the Sigma standard with so-called "response actions" that can get executed after a rule match
- It supports multiple output channels: the Windows Eventlog, a log file and remote UDP targets
Its documentation can be found at aurora-agent-manual.nextron-systems.com.
188.8.131.52. Aurora Overview¶
Service Control >
Asset View (Deployed) the overview of all assets with installed Aurora is shown. Clicking on the entry opens a drop-down menu with details and additional information.
184.108.40.206. Deploy Aurora on Asset¶
Analogous you can see an overview of all assets without Aurora installed under
Service Control >
Asset View (Not Deployed) and install Aurora using the
Deploy Aurora button.
220.127.116.11. Change Service for an Asset¶
To change the Aurora configuration of an asset, navigate to
Service Control >
Asset View (Deployed), select the asset's checkbox and choose
Change Aurora Configuration. Then choose the desired service configuration by clicking
Assign and Restart.
If you want to enable or disable the Aurora service on an asset, select it with the checkbox and use the
Disable button or select the play or stop action icon on single assets.
18.104.22.168. Creating a Custom Service Configuration¶
Service Control >
Add Configuration, enter a name and add the rulesets that should apply for this service configuration. No rulesets is a viable option, if you only want to use the non-sigma matching modules. You don't need to edit any other option as sane defaults are given.
22.214.171.124. Process Excludes¶
If Aurora uses too much CPU cycles, the most common reason is a heavy event producer on the system (e.g. anti virus or communication software). In order to analyse the issue and define process exclusions, go to
Service Control >
An overview over the top event producing processes is given on the bottom of the section. Another possibility is to collect diagnostic packs of systems in question and look in the
status.txt at the event statistics by process.
126.96.36.199. False Positive Filters¶
If needed, false positives can be globally filtered on all Aurora agents at
Service Control >
False Positive Filters. It is recommended to filter false positives at
Servce Control >
Rules and filter the false positives on a rule level using the "edit false positive" action (funnel icon). For more details see section False Positive Filters of Sigma Rules. If this is not possible, because you need a quick fix and multiple rules are affected, the global false positive filter can help.
A too permissive filter will greatly reduce Aurora's detection and response capabilities.
188.8.131.52. Response Action Logs¶
You can view an overview and the logs of the Aurora response and simulated response actions under
Service Control >
Response Action Logs.
184.108.40.206. Best Practices for Managing Aurora¶
- Install the ASGARD agent on the asset (see section ASGARD Agent Deployment)
- Install the ASGARD service controller on the asset (see section Service Controller Installation)
- Deploy the Aurora Service on the asset using the
[Default] Standard configuration with critical and high Sigma rulesconfiguration (see section Deploy Aurora on Asset)
If you want to enable the blocking capabilities of Aurora, we suggest to enable our included responses:
- See the overview at
Effective Rules and Responserow shows how many responses are active. By default no responses are active. See section How to activate Responses on how to activate responses.
- Do not directly activate the responses in production environments. Monitor your environment for at least a month with simulated responses to verify that no false positive matches occur.
- In larger environments use different configurations and rulesets for different environments. As an example you can test changes to the configuration in a test environment, before adapting the changes for the production environment.
You can test the response functionality by entering the command
rundll32.exe AuroraFunctionTest.dll StartW
on the command line of an asset. As a result you should see following message in the
Service Control >
Response Action Logs:
More tests are available from the Function Tests section of the Aurora manual. Those tests only generate detection events but no responses. If your ASGARD Management Center is connected to an Analysis Cockpit, you can see the detection events at
Aurora Events or in the Windows EventLog of the asset.
4.7.5. LogWatcher Service¶
The LogWatcher real-time service monitors the Windows Event Log using predefined rules in the Sigma format and creates an alert that is forwarded to ASGARD Analysis Cockpit if a match was found. The LogWatcher service is no longer shown by default on newly installed ASGARDs. To enable it go to
Advanced and enable the
Show LogWatcher checkbox.
In order to make full use of ASGARD LogWatcher you need a Windows Audit Policy and Sysmon, both with a reasonable configuration, in place. We expect organizations to take care of providing a sane configuration by their own. This section helps in giving starting points, if needed.
220.127.116.11.1. Windows Audit Policy¶
The default audit policy of Windows is not suitable for security monitoring and needs to be configured. There are Microsoft recommendations available online.
Also auditing the command line for process creation events should be enabled. Documentation for that task is available here.
18.104.22.168.2. Sysmon Configuration Template¶
There are some best practise configurations available. See them as a good starting point to develop your own configuration. If you do not have a Sysmon configuration yet, there are several options we suggest:
- The Nextron Systems fork of SwiftOnSecurity's sysmon-config
- The SwiftOnSecurity sysmon-config
- Olaf Hartong's sysmon-modular
In general we suggest our own configuration, as we test our rules with it and include changes from the upstream configuration. But depending on your preferences, either of those listed configurations is a good starting point for writing your own configuration.
Do not deploy those configurations to your production environment without prior testing.
It is expected that some tools you use will be the source of huge log volume and should be tuned in the configuration depending your environment.
22.214.171.124.3. Sysmon Installation¶
Sysmon is part of Microsoft Sysinternals and therefore has to be installed as a third party tool. The preferred way to distribute Sysmon and its configuration is using your organization's device management. If you do not have access to one, you can use ASGARD's playbook feature to distribute Sysmon and update its configuration. Documentation which describes the playbook creation and that offers maintenance scripts can be found in our asgard-playpooks repository.
This chapter explains how to configure LogWatcher using Sigma rules.
126.96.36.199.1. LogWatcher Overview¶
Service Control >
Asset View (Deployed) the overview of all assets with an installed LogWatcher is shown. Clicking on the entry opens a drop-down menu with details and additional information.
Analogous you can see an overview of all assets without an installed LogWatcher under
Service Control >
Asset View (Not Deployed).
188.8.131.52.2. Enable Service for an Asset¶
To enable the LogWatcher service for an asset, navigate to
Service Control >
Asset View, select the asset's checkbox and choose
Assign Configuration. Then choose the desired service configuration by clicking
184.108.40.206.3. Creating a Custom Service Configuration¶
A service configuration is used to group assets of similar type and assign them a set of rules (in form of rulesets).
Service Control >
Add Configuration, enter a name and add the rulesets that should apply for this service configuration (i.e. group of assets).
If you have not configured a ruleset yet, you need to do so beforehand.
4.8. IOC Management¶
4.8.1. Integrating Custom IOCs¶
IOC Management gives you the opportunity to easily integrate custom signatures into your scans.
In order to create your own custom IOC Group, navigate to
IOC Management >
Add IOC Group in the upper right corner. Select a name and optionally a description for your IOC Group.
To add IOCs to this group, use the
Show and edit IOCs in this IOC group action. A side pane opens where you can click the
Import IOCs button to import your own signatures in any of THOR’s IOC formats as files (e.g. files for keyword IOCs, YARA files and SIGMA files). Refer to the
THOR manual (custom signatures) for a complete list and file formats. Browse to the file you want to add and click upload. This adds your IOC file to the default ruleset.
However, you can also click the
Add IOC(s) button to add some IOCs interactively. Select the type, score and description, enter some values and click the
Add IOC button.
You can add those IOC Groups to IOC Rulesets which can be created in the
IOC Management >
IOC Rulesets tab by clicking the
Add Ruleset button in the upper right corner. Select name and description and click the
Add Ruleset button.
After that, click on an entry in the table to expand it. There you get information about all IOC Groups which have been added to this ruleset. Additionally you can add or remove selected IOC Groups in
IOC Management: IOCs by clicking one of the three buttons shown below.
Those rulesets can be selected in the "Custom Signature" field while creating a new scan job. If a ruleset is selected, the scan will include all custom IOCs included in IOC Groups which have been added to this ruleset. You can also select more than one ruleset.
4.8.2. Integrating IOCs through MISP¶
ASGARD provides an easy to use interface for integrating IOCs from a connected MISP into THOR scans. In order to add rules from a MISP, navigate to
IOC Management >
MISP Events, select the IOCs and add them to the desired ruleset by using the button in the upper right corner.
There is no default ruleset for MISP. You must create at least one ruleset (see tab "MISP Rulesets") before you can add MISP rules.
In order to create a ruleset, click
Add MISP Ruleset in the
IOC Management >
MISP Rulsets tab. Select a name and the type of IOCs you want to use in this ruleset. By default, all types are selected, but there may be reasons for deselecting certain categories. For example, filename IOCs tend to cause false positives and may be deselected for that reason. The picture below shows the dialogue for adding a MISP ruleset. Enable Auto Generate in order to automatically compile new MISP events into the ruleset, when they arrive.
In order to use a MISP ruleset in a scan: Add the ruleset in the
MISP Signatures field when creating your scan.
4.9. Evidence Collection¶
4.9.1. Collected Evidences¶
ASGARD provides two forms of collected evidence:
- Playbook output (file or memory collection, command output)
- Sample quarantine (sent by THOR via Bifrost protocol during the scan)
All collected evidence can be downloaded in the
Collected Evidence section.
ASGARD requires an Issuer-License in order to scan systems. The Issuer-License contains the number of asset-, server- and workstation systems that can be scanned with ASGARD Management Center as well as the Aurora or LogWatcher service licenses.
ASGARD will automatically issue a valid single-license for a particular system during its initial THOR scan.
The screenshot below shows the licensing section of an ASGARD.
In addition, ASGARD can create single-licenses that can be used for agentless scanning. In this case the license is generated and downloaded through the Web frontend.
The following systems require a workstation license in order to be scanned:
- Windows 7 / 8 / 10 / 11
- Mac OS
The following systems require a server license in order to be scanned:
- All Microsoft Windows server systems
- All Linux systems
4.11.1. Provide an THOR Incident Response License (optional)¶
In case you have an THOR Incident Response license and want to use it with ASGARD, just upload it through the web based UI. This will remove all endpoint count restrictions from ASGARD. You can scan as many endpoints as you like – regardless of the type (workstation / server).
4.12.1. ASGARD Updates¶
ASGARD will search for ASGARD updates on a daily basis. Available updates will automatically be shown in the section
As soon as an ASGARD update is available, a button
Upgrade from ... to ... appears. Clicking this button will start the update process. The ASGARD service will be restarted and the user will be forced to re-login. Generally update MASTER ASGARD before the connected ASGARDs.
4.12.2. Updates of THOR and THOR Signatures¶
By default, ASGARD will search for signature updates and THOR updates on an hourly basis. These updates will be set to active automatically. Therefore, a triggered scan will always employ the current THOR version and current signature version. You may disable or modify the automatic THOR and Signature updates by deleting or modifying the entries in this section.
It is possible to intentionally scan with an old scanner version by clicking on the pencil icon and selecting the respective version from the drop-down menu.
Please be aware, that this is a global setting and will affect all scans!
4.12.3. Agent Updates¶
If an asset or an agent can be update, there will be a notice shown in the
4.13. User Management¶
Access user management via
Users. This section allows administrators to add or edit user accounts.
Editing a user account does not require a password although the fields are shown in the dialogue. An initial password has to be provided for user creation, though.
Access the user roles in
By default, ASGARD ships with the following pre-configured user roles. The pre-configured roles can be modified or deleted. The ASGARD role model is fully configurable.
Note that all users except users with the right
Readonly have the right to run scans on endpoints.
The following section describes these predefined rights and restrictions that each role can have.
|Manage Scan Templates|
|Allows scan templates management|
|Connect to endsystems via remote console|
|View Remote Console Log|
|Review the recordings of all remote console sessions|
|Run playbooks, including playbooks for evidence collection, to kill processes or isolate an endpoint|
|User can manage services on endpoint, e.g. Aurora or LogWatcher|
|Force Scan Template|
|Force user to use predefined scan templates that are not restricted|
|No Inactive Assets|
|Cannot view inactive assets in asset management.|
|No Task Start|
|Cannot start scans or task (playbooks)|
|Can't change anything, can't run scans or response tasks. Used to generate read-only API keys|
4.13.4. LDAP Configuration¶
In order to configure LDAP, navigate to
LDAP. In the left column you can test and configure the LDAP connection itself.
In the right column, the mapping of LDAP groups to ASGARD groups (and its associated permissions) is defined.
First check if your LDAP server is reachable by ASGARD by clicking "Test Connection".
Then check the bind user you want to use for ASGARD. Read permissions on the bind user are sufficient.
To find out the distinguished name you can use an LDAP browser or query using the PowerShell AD module command
Next configure the LDAP filters used to identify the groups and users and their preferred attributes in your LDAP structure. A default for LDAP and AD in a flat structure is given in the "Use recommended filters" drop-down menu, but you can adapt it to your liking. The test button shows you if a login with that user would be successful and which groups ASGARD identified and could be used for a mapping to ASGARD groups.
If you need to adapt the recommended configuration or want to customize it, we recommend an LDAP browser such as ADExplorer from Sysinternals
to browse your LDAP structure. As an example you could use your organisation's e-mail address as a user login name if you change the "User Filter"
You need to save the configuration by clicking
Update LDAP Config.
Using the test buttons only uses the data in the forms, but does not save it, so that you can use it for testing purposes anytime, without changing your working configuration.
After the LDAP configuration is set up, you need to provide role mapping from LDAP groups to ASGARD groups.
This is done in the right column by using the
Add LDAP Role feature.
Enabling LDAP authentication disables personal API keys, password changes and 2FA for all user accounts except admin. (LDAP users cannot use said features).
4.14. Other Settings¶
4.14.1. Syslog Forwarding¶
Syslog forwarding can be configured in
RSYSLOG. To add a forwarding for local log source click
Add Rsyslog Forwarding.
The following log sources can be forwarded individually:
|ASGARD Log||Everything related to the ASGARD service, processes, task and scan jobs|
|ASGARD Audit Log||Detailed audit log of all user activity within the system|
|Agent Log||All ASGARD agent activities|
|THOR Log||THOR scan results (available if scan config has
4.14.2. TLS Certificate Installation¶
Instead of using the pre-installed self-signed TLS Certificate, users can upload their own TLS Certificate for ASGARD.
In order to achieve the best possible compatibility with the most common browsers, we recommend using the system’s FQDN in both fields
Common Name AND
Please note that generating a CSR on the command line is not supported.
The generated CSR can be used to generate a TLS Certificate. Subsequently, this TLS Certificate can be uploaded in the
4.14.3. Manage Services¶
The individual ASGARD services can be managed in
Services. The services can be stopped or restarted with the respective buttons in the
4.14.4. NTP Configuration¶
The current NTP configuration can be found in the NTP sub-section.
A Source Pool or Source Server can be removed by clicking the delete action. To create a new Source Pool or Source Server, click
Add NTP Source in the upper right corner.
4.14.5. Settings for Bifrost¶
Bifrost allows you to automatically upload suspicious files to your ASGARD during a THOR scan. If an Analysis Cockpit is connected, these files get automatically forwarded to the Analysis Cockpit in order to drop them into a connected Sandbox system. However, the collected files will stay on ASGARD for the amount of time specified in
Retention time (0 days represent an indefinite amount of time).
The collected files can be downloaded in the
Evidence Collection section. All files are zip archived and password protected with the password
In order to automatically collect suspicious files, you have to create a scan with Bifrost enabled. Check the
Send Suspicious Files to ASGARD option to send samples to the system set as
bifrost2Server. Use the placeholder
%asgard-host% to use the hostname of you ASGARD instance as the Bifrost server.
This will collect all files with a score of 60 or higher and make them available for download in ASGARDs
Collected Files section.
For Details on how to automatically forward to a sandbox system please refer to the Analysis Cockpit manual.
4.14.8. Change Proxy Settings¶
In this dialogue, you can add or modify ASGARDs proxy configuration. Please note, you need to restart the ASGARD service (Tab Services) afterwards.
The Advanced tab lets you specify additional global settings. The session timeout for web-based UI can be configured. Default is one hour. If
Show Advanced Tasks is set, ASGARD will show system maintenance jobs (e.g. update ASGARD Agent on endpoints) within the response control section.
Inactive assets can be hidden in the Asset Management Section by setting a suitable threshold for
Hide inactive Assets.
4.15. User Settings¶
4.15.1. Changing your password¶
To change your password, navigate to the
User Settings section.
4.15.2. API Key¶
This section also allows you to set and modify an API key.
Note that currently an API key always has the access rights of the user context in which it has been generated. If you want to create a restricted API key, add a new restricted user and generate an API key in the new user's context.
4.16. Uninstall ASGARD Agents¶
The following listings contain commands to uninstall ASGARD Agents on endpoints.
The commands contain names used by the default installer packages. In cases in which you've generated custom installer packages with a custom service and binary name, adjust the commands accordingly.
4.16.1. Uninstall ASGARD Agents on Windows¶
sc stop asgard2-agent sc delete asgard2-agent sc stop asgard2-agent_sc sc delete asgard2-agent_sc del /F /Q C:\Windows\System32\asgard2-agent
Line 3 and 4 are only necessary if the new service controller (on ASGARD 2.11+) has been installed.
4.16.2. Uninstall ASGARD Agents on Linux¶
yum remove 'asgard2-agent*'
apt-get remove 'asgard2-agent*'
/usr/sbin/asgard2-agent-amd64 stop /usr/sbin/asgard2-agent-amd64 uninstall rm -rf /usr/sbin/asgard2-agent-amd64 rm -rf /var/tmp/nextron/asgard2-agent rm -rf /var/lib/nextron/asgard2-agent
4.16.3. Uninstall ASGARD Agents on macOS¶
sudo /var/lib/asgard2-agent/asgard2-agent --uninstall sudo rm -rf /var/lib/asgard2-agent/asgard2-agent
4.17. Uninstall ASGARD Service Controller¶
The command contains names used by the default installer packages. In cases in which you've generated custom installer packages with a custom service and binary name, adjust the commands accordingly.
If you want to uninstall the ASGARD Service Controller and Agent, see section Uninstall ASGARD Agents.
If you only want to uninstall the ASGARD Service Controller execute: