4

Agentless Assets

Last Update 3 months ago

Agentless Asset Onboarding Jump/Bastion Host Setup How to Configure WinRM over HTTPS (Port 5986) On-Prem - Agentless Target Machine Prerequisites Check

Agentless Asset Onboarding

Introduction

This section provides detailed instructions for onboarding assets to the SecOps Solution On Prem Platform using both agent-less method.

Pre-requisites for Onboarding Assets

  1. Windows Based Systems

    1. WinRM Service:

      • Ensure WinRM service (HTTP) is running on port 5985 on the target host machine. (Command: winrm quickconfig)
      • Inbound rule on port 5985 is enabled on the Windows machine to allow connections from the Central Server or Jump Server (if onboarding via a Jump Server)

  2. Linux Based System:

    • SSH Service:
      • Ensure SSH service is configured and running on the Linux host.
      • Ensure that the target machine is reachable from the Central Server (or Jump Server, if onboarding via a Jump Server) on the port where SSH is running. By default, SSH runs on port 22. If SSH is configured on a custom port, please ensure the same port is configured on the platform accordingly. Also, make sure an inbound firewall rule is in place on this SSH port to allow connections from the Central Server / Jump Server.


Outbound HTTP/HTTPS:
Allow outbound from the target machine to:
 - SecOps Central Server on port 5679 (HTTP), 5680(HTTPS)  or
 - SecOps Jump Host on port 5679 (HTTP), 5680(HTTPS)

Steps:

1. Navigate to the Asset Module

  • In the top navigation panel of the SecOps platform, click on the Asset module to access the asset management functionality.

2. Initiate the Onboarding Process

  • Click on Add Asset to open the asset onboarding window.

  • Select the Agent-less option, which allows you to onboard assets without installing an agent on the target device.

3. Provide Asset Information

  • IP Address: Specify the asset’s network IP address to facilitate identification and connection.

  • Credentials: Provide the required authentication details (Username/Password or SSH Key) to enable the platform to access the asset and perform an authenticated scan.

    Note: For Unix-based systems, please ensure that the specified user account has passwordless sudo privileges enabled to support authenticated vulnerability scanning and patch deployment.

  • Operating System: Select the operating system of the asset from the available options.

  • Asset Groups: Optionally, assign the asset to one or more asset groups to help categorize and manage it effectively.

  • Criticality Level: Set the asset’s criticality level to determine its importance and impact in your operations.

4. Validate Connectivity and Complete Onboarding

  • After entering the asset details, click on Add Asset to initiate the connection validation process.

  • The platform will attempt to establish connectivity with the asset. Once successful, it will automatically onboard the asset, making it available for monitoring and management within the platform.

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us