.png?sv=2019-07-07&sig=%2F6mCvESJkWDeGqH0yi1M6Hwp0VoJLpy6ExuBMYwUIpY%3D&spr=https%2Chttp&st=2023-03-30T13%3A29%3A20Z&se=2023-03-30T13%3A39%3A20Z&srt=o&ss=b&sp=r){kind=logo}
Medigate
- 18 Oct 2022
- 1 Minute to read
-
Print
-
DarkLight
-
PDF
Medigate
- Updated on 18 Oct 2022
- 1 Minute to read
-
Print
-
DarkLight
-
PDF
Medigate is a medical device security platform that protects connected medical devices on health care provider networks, allowing inventory management and facilitating detection and prevention capabilities.
The Medigate adapter connection requires the following parameters:
- Medigate Domain – Enter the hostname of the Medigate server. When hosted by Medigate, the hostname used for API access with a token is
api.medigate.io - User Name and Password (For old API) (optional) – The user name and password for the user used in the connection. Use this when you are connecting using the older version of the API.
- API Token (for new API) (optional) - the API token - use this when you are connecting using the new API.
- Verify SSL – Select whether to verify the SSL certificate of the server.
- HTTPS Proxy (optional) – Connect the adapter to a proxy instead of directly connecting it to the domain.
Advanced Settings
Note:
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.
- CIDR Exclusion List (optional) - Specify in a comma-separated list the CIDR ranges of assets that you want to exclude from the fetch.
Note:
To learn more about Adapter Configuration tab advanced settings, see Adapter Advanced Settings.