HSLAB Security Tracker NESB

How to Configure HSLAB Security Tracker NESB HSLAB Security Tracker NESB (Network Element Security Boundary) is a powerful tool designed to monitor network activity, track security events, and secure your system boundaries. Proper configuration ensures optimal performance and robust protection against unauthorized access. This guide provides a straightforward, step-by-step approach to setting up your security tracker. Prerequisites Before Setup

Before beginning the configuration process, ensure you have completed the following steps:

Administrator Privileges: Log into the hosting system with full root or administrative rights.

Network Topology Map: Have a clear list of your internal IP ranges and external boundary interfaces.

System Requirements: Verify that your hardware meets the minimum storage and processing specifications for logging traffic. Step 1: Initial Installation and Licensing

Activate the software core to prepare the environment for your custom rules.

Run the HSLAB Security Tracker installer package on your gateway or designated monitoring server.

Follow the on-screen prompts to select the installation directory. Launch the application management console.

Navigate to Help > License Management and enter your NESB registration key. Restart the service to apply the license parameters. Step 2: Define Network Interfaces

Inform the software which networks are safe and which ones require strict monitoring. Open the Configuration menu from the main dashboard. Select the Network Interfaces tab.

Identify your Local Area Network (LAN) interface and label it as Trusted (Internal).

Identify your Wide Area Network (WAN) or internet-facing interface and label it as Untrusted (External).

Click Apply to bind the monitoring engine to these specific adapters. Step 3: Configure Boundary Rules and Alerts

Set the security parameters to detect and log suspicious network behavior. Navigate to the NESB Policy Engine section.

Click Add New Rule to establish a baseline filtering policy.

Set the default action for unknown external incoming traffic to Block and Log. Move to the Alert Notifications tab.

Enter your network administrator’s email address or your central Syslog server IP address.

Check the boxes for Critical Events and Boundary Breaches to trigger immediate alerts. Step 4: Database and Storage Tuning

Optimize how the system saves event logs to prevent performance bottlenecks. Go to Options > Database Settings.

Choose your preferred database backend (the built-in engine is sufficient for small networks, while SQL is recommended for large enterprises).

Set the Log Retention Policy to your required compliance duration (e.g., 90 days).

Enable Log Rotation to automatically archive old data when the disk reaches 80% capacity. Step 5: Verify the Configuration

Test the system to ensure it actively tracks security events. Open the Real-Time Monitor window in the HSLAB console.

Generate test traffic from an external IP address, such as a controlled ping or port scan.

Confirm that the activity appears immediately in the security tracker log with the correct “Untrusted” classification.

Check your inbox or Syslog server to verify that the test alert arrived successfully. To help tailor this guide further, let me know: What operating system are you hosting the software on?

Are you integrating this with an external SQL database or a Syslog server?

What specific network size or traffic volume are you planning to monitor?

I can provide specific scripts, optimization commands, or troubleshooting steps based on your environment.