- 02 Aug 2022
- 1 Minute to read
Remediant SecureONE (JITA)
- Updated on 02 Aug 2022
- 1 Minute to read
Remediant SecureONE is a Just-In-Time Privileged Access Management (JITA) solution that enables control and insight over the distribution, usage, and protection of privileged access across enterprise environments.
Host Name or IP Address (required) - The hostname or IP address of the Remediant SecureONE server.
User ID and API Token (required) - The credentials for a user account that has the Required Permissions to fetch assets.
Verify SSL - Select to verify the SSL certificate offered by the value supplied in Host Name or IP Address. For more details, see SSL Trust & CA Settings.
HTTPS Proxy (optional) - A proxy to use when connecting to the value supplied in Host Name or IP Address.
HTTPS Proxy User Name (optional) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.
HTTPS Proxy Password (optional) - The password to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.
For details on the common adapter connection parameters and buttons, see Adding a New Adapter Connection.
From Version 4.6, Advanced settings can either apply for all connections for this adapter, or you can set different advanced settings and/or different scheduling for a specific connection, refer to Advanced Configuration for Adapters.
- Number of requests to perform in parallel (required, default: 50) - Specify the maximum parallel request all connections for this adapter will create when connecting the SecureONE server.
- Fetch full devices data
- If enabled, all connections for this adapter will fetch full devices data including the local admins from Remediant SecureONE.
- If disabled, all connections for this adapter won't fetch full devices data from Remediant SecureONE.
- Ignore device without last seen - Select to ignore devices that have no Last Seen information.
For details on general advanced settings under the Adapter Configuration tab, see Adapter Advanced Settings.
Axonius uses the SecureONE API.
The value supplied in User ID and API Token must have Read access to devices.
User ID refers to the internal ID of a SecureONE user the application wants to assume. The API key must be created with that User ID.