Cynet 360
About Cynet 360
Cynet XDR prevents and detects threats on endpoints, networks, and users--and triggers for each identified threat an automated investigation flow that reveals the attack’s scope and root cause, and applies automated remediation. The 24×7 MDR team continuously monitors and optimizes this process to maintain top quality and precision.
Why You Should Integrate Cynet 360
The Cynet source pulls host information from each agent to ensure you have the most coverage from this EPP.
The Data We Collect and How We Use It
The table below lists the fields we collect from Cynet and how they map to the fields in our Sevco platform. This data is only used internally; we do not share it with any parties outside of Sevco. Refer to our privacy policy for details.
| Cynet 360 field | Sevco Field |
|---|---|
Clientdbid | ID |
Hostname | Hostnames |
LastIP | IPs |
OperatingSystem | OS |
LastScan | LastUpdatedTime |
Integrate Cynet 360
-
Add a source: Follow our instructions to add a Sevco source.
-
Provide credentials: You'll be asked to provide source credentials that Sevco will use to connect to Cynet 360:
| Parameter Name | Parameter Description | Where to Find the Parameter Value |
|---|---|---|
| username | Username of Cynet 360 user with API access. | Manage Cynet users in the Cynet Settings panel's Users page. Refer to the Cynet User Guide's "Add New User" section for more details. |
| password | Password of Cynet 360 user with API access. | Manage Cynet users in the Cynet Settings panel's Users page. Refer to the Cynet User Guide's "Add New User" section for more details. |
| client_id | This is a number. Example: '2414141' | This is provided by Cynet representatives. |
| scan_group_name | If blank, the source will pull all available devices; otherwise pull devices only associated with the specified scan group. | Manage Scan Groups in the Cynet Settings panel's Scan Groups page. For more information about scan groups, refer to the Cynet User Guide's "Scan Groups" section. |
- Set permissions: In Cynet 360, ensure the user is in a security group with "API - Full Access" permissions.
If you encounter any errors, they are most likely related to incorrect credentials or insufficient permissions. Verify your work in steps 2 and 3.
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].
Updated 7 months ago