Remediant SecureONE


Remediant SecureONE is an agentless Lateral Movement Prevention solution that administers dynamic Just-in-Time (JIT) privileged account access to help customers achieve Zero Standing Privilege.

Why You Should Integrate

Integrating with Remediant SecureONE will provide visibility and device presence awareness for an environment to identify Remediant coverage.

How Does the Integration Work

This integration pulls data about Remediant SecureONE devices that meets the following criteria.

  • = True
  • lastScan.success = True
  • last_scanned >= 30 days ago

This data is only used internally; we do not share it with any parties outside of Sevco. Refer to our privacy policy for details.


  1. Install a runner: Follow our instructions to install a runner.

  2. Choose a runner: Select the runner you would like to use for retrieving data from the source.

    • Requirements:
      • TCP/IP 443 from Runner to the SecureONE server.
  3. Configure plugin: Configure the plugin with the required fields.

URL*The hostname or IP address of the Remediant SecureONE
Skip TLS Certification ValidationSkip certificates validation when using a certificate that is self-signed or unable to be validated through a proper certificate authority.
User ID*The internal ID of a SecureONE user (Linked User) the application will use.5ab4c88683ef55d59b47f0Xx
API Key*The issued API key***********************
  1. Configure Name: OPTIONAL: You can give the configuration a name to provide an identifiable attribute of the configuration to delineate other similar configurations.

  2. Activate Config: To enable this configuration and begin pulling data select "Activate". If you wish to save the configuration to come back later to finish, select "Save Draft". This will save the configuration, but keep it disabled until Activated.

Source Documentation

Creating credentials

You'll be asked to provide source credentials that Sevco will use to connect to Remediant SecureONE. The User ID is an internal ID (Linked Users) of a SecureONE user that the application will use and is provided when the API key is generated.

Required Permissions

User Linked and API Key must have read access to devices (also referred to as computers).

API Documentation

Contact Us

If you're having problems integrating a source, or if you've found something wrong in this document, please email us at [email protected].

Tags: on-prem