Gartner Peer Insights


1.1. API for interaction with Labyrinth Deception Platform 

We added a REST API to obtain the necessary data when working with Labyrinth Deception Platform. Currently, the following information can be obtained using this interface:  

  1. License status information;  
  2. List of tenants;  
  3. List of Nodes that are part of the installation (Admin Console and all available Worker Nodes and their statuses);  
  4. List of Honeynet for the tenant;  
  5. Points list for the tenant;  
  6. List of Seeder Agents and Seeder Tasks for the tenant;  
  7. List of alerts;  
  8. Change the status of an alert. 

   In the subsequent releases, we plan to expand the functionality of this API. 


After the update, a detailed description of the REST API is available here: 



Authentication to access this interface is performed using an API token that is generated for the user in Settings -> Users.

The token can be generated:

  1. By a user for themself;
  2. An administrator for themself or for another user in the tenant;
  3. Superuser for themself or for another user in any tenant;

Generating a token by an ordinary user involves the following sequence of actions:

  1. Go to “Settings -> Users -> Edit Current User"
  2. Click on “Issue API Token"

   A token is available for viewing only once. Therefore, once the modal window with the token is closed, it cannot be viewed again. Therefore, saving this token in a safe and secure place is necessary.

Each user can have only one token. If the token creation procedure is started again as described above, the old token will be invalidated.

To generate a token for another user, you need:

  1. Go to “Settings -> Users"
  2. Select the required user from the list and edit its settings.
  3. In the dialog box that opens, select “Issue API Token"

    Only users with the Administrator role or Superusers can generate tokens for other users.


1.2.  MITRE ATT&CK® Matrix mapping

The system's alert information is supplemented by a description of the attacker's actions using the tactics and techniques described in the MITRE ATT&CK® matrix.

Techniques and tactics that appear in the alert description are links to the official MITRE website, where you can read a detailed description of a particular tactic or technique.

If SIEM integration is enabled and configured, information about tactics and techniques is also added to the CEF message.

Currently, alert compliance with MITRE ATT&CK® matrices covers a specific list of tactics from ATT&CK for Enterprise and ICS.

The MITRE ATT&CK® for Enterprise list includes the following tactics:

  • TA0001  Initial Access
  • TA0002  Execution
  • TA0003  Persistence
  • TA0005  Defense Evasion
  • TA0006  Credential Access
  • TA0007  Discovery
  • TA0008  Lateral Movement
  • TA0009  Collection
  • TA0043  Reconnaissance

The techniques and sub-techniques include the following:

  • T1046 Network Service Discovery
  • T1057 Process Discovery
  • T1059 Command and Scripting Interpreter
  • T1069 Permission Groups Discovery
  • T1070.003 Indicator Removal: Clear Command History
  • T1078 Valid Accounts
  • T1082 System Information Discovery
  • T1083 File and Directory Discovery
  • T1087 Account Discovery
  • T1110 Brute Force:
    • T1110.001 Brute Force: Password Guessing
  • T1135 Network Share Discovery
  • T1136 Create Account
  • T1190 Exploit Public-Facing Application
  • T1210 Exploitation of Remote Services
  • T1212 Exploitation for Credential Access
  • T1557 Adversary-in-the-Middle:
    • T1557.001 LLMNR/NBT-NS Poisoning and SMB Relay
    • T1557.002 ARP Cache Poisoning
  • T1590.002 Gather Victim Network Information: DNS
  • T1592.002 Gather Victim Host Information: Software
  • T1595 Active Scanning:
    • T1595.002 Active Scanning: Vulnerability Scanning
    • T1595.003 Active Scanning: Wordlist Scanning
  • T1602 Data from Configuration Repository:
    • T1602.001 Data from Configuration Repository: SNMP (MIB Dump)

Tactics and techniques that correspond to the MITRE ATT&CK® for ICS matrix:

  • TA0100  Collection
  • TA0102  Discovery
  • TA0108  Initial Access
  • T0801  Monitor Process State
  • T0846  Remote System Discovery
  • T0866  Exploitation of Remote Services

1.3.  Improved CEF message data for SIEM integration via syslog

If the SIEM Integration (Syslog forwarder) integration is enabled in theintegations settings, alerts and the Audit Log are sent to the SIEM in CEF format.

This release adds information about the information sent to the SIEM:

  1. MITRE ATT&CK® tactics and techniques (cs3 and cs4, respectively);
  2. Point Type of the attacked Point (pointType);
  3. The Honeynet to which the attacked Point belongs (honeynetID);
  4. Honeynet location to which the attacked Point belongs (location).

For example,

CEF:0|Labyrinth Technologies|Point|0|LAB_ALERT|RCE detected|10|src= dst= pointType=uweb_comments_test honeynetID=honeynet01 location=labdev dvc= dvchost=sierra deviceExternalId=universalweb-a6f05252 cs3=TA0008 cs3Label=Tactic cs4=T1210 cs4Label=Technique cs1=Remote Code Execution attempt has been detected cs1Label=Description cs2=Identify the host of the source IP. Check previous activity from source IP. Recommendation: continue monitoring activity from source IP. cs2Label=Playbook

1.4.  Information about the username you are creating or editing

Information about the user's username being created or edited has been added to the Audit Log records sent to the SIEM. Prior to this release, this information could only be obtained from the Labyrinth web interface.

Currently, the audit log sent to the SIEM is extended and looks like this:

CEF:0|Labyrinth Technologies|Tenant|0|LAB_AUDIT|add_new_user|10|src= event_type=add_new_user tenant=bubble username=vlakas target_username=test_user event_status=success

1.5.  WAF for Universal Web Point

A full-fledged Web Application Firewall has been added to Universal Web Point to detect the types of attacks more accurately on the Point itself, including both OWASP Top 10 and other vulnerabilities.

At the same time, the detected attacks do not affect the web application with which the Point is associated.

WAF uses the OWASP® Core Rule Set (CRS) to detect attacks, a set of rules for detecting common attacks on Web applications and includes, among other things, the OWASP Top Ten.

The categories of detection rules include the following:

  • SQL Injection (SQLi)
  • Cross Site Scripting (XSS)
  • Local File Inclusion (LFI)
  • Remote File Inclusion (RFI)
  • PHP Code Injection
  • Java Code Injection
  • HTTPoxy
  • Shellshock

1.6.  Expanding Universal Web Point configuration options

The list of updates includes the expansion of Point settings and includes the following:

  1. Setting up TLS certificates.

You can add your TLS certificate and the key that will be used for HTTPS.

By default, when launching a Universal Web Point, a self-signed certificate is used, which is generated automatically based on the certificate parameters of the original web application.

Currently, you can set your TLS certificate and key directly in the configuration.

  1. Setting up Rate Limit.

In the Universal Web Point configuration, you can set the settings to limit the intensity of requests, which reduces the overall load on the host specified in upstream_url.

  1. Setting up additional URL paths

It is possible to add URL paths that are not present in the original web application. For example, the original web application does not have /robots.txt, and Universal Web Point can respond to such requests with specific content.

For example:



    upstream_url: https://labyrinth.tech

    server_name: labyrinth.tech

    service_type: iis

    server_banner: The latest MS IIS


      X-Powered-By: "ASP.NET"


      - path: /robots.txt

        module: text


          - GET

        contents: |

          User-agent: *

          Disallow: /admin

          Disallow: /cabinet

          Disallow: /error/


  1. ARP spoofing detection.
    Added ARP spoofing attack detection.

    All of the above examples are for illustrative purposes only and may not be accurate. Please refer to the Universal Web Point configuration documentation for specific configuration options.


1.7.  Improvements to ClientOS

ClientOS is a type of Point that simulates user actions on the network. For example, it makes HTTP/S, NetBIOS, DNS, and other requests for services specified in the Point configuration at a specific frequency, which can be configured in a new release.

For example:



    enable: true


    enable: true


      - www.bing.com

      - sls.update.microsoft.com

      - v10.vortex-win.data.microsoft.com

      - _ldap._tcp.dc._msdcs.WORKGROUP.localdomain

      - detectportal.firefox.com

timeout: 10

timeout_shift: 5


    enable: true

    verify_tls: false

    user_agent: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36"


      - http://detectportal.firefox.com/canonical.html

      - https://profile.accounts.firefox.com

      - https://token.services.mozilla.com

      - https://api.accounts.firefox.com

    timeout: 60

    timeout_shift: 5


  • timeout - is the time interval between requests, specified in seconds;
  • timeout_shift - is the number of seconds that controls the time interval error.

For example, if timeout = 60 and timeout_shift = 5, the next request may be made not exactly in 60 seconds, but, for example, in 61, 65, 63, etc. seconds.

    All of the above examples are for illustrative purposes only and may not be accurate. Please refer to the ClientOS Point configuration documentation for specific configuration options.

Subscribe to our Newsletter

You successfully subscribed!