Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Design Guide—Cybersecurity for Computer Vision Solutions
Introduction Validation design concepts and requirements Solution architecture Validation
Computer vision platform
Integration validation
Performance validation
Vulnerability detection
Sizing the solution Backup and restore operations Monitoring the solution Troubleshooting recommendations Summary and conclusions References

Integration validation

Home > Workload Solutions > Computer Vision > Guides > Design Guide—Cybersecurity for Computer Vision Solutions > Integration validation

Integration validation

  • Secureworks VDR and XDR were easy to install and configure in our virtualized VMS plus CV environment. The primary factor in designing for the on-premises components is to ensure there is low latency and reliable communication when sending data collected locally to Secureworks services hosted on AWS for analysis.


    VDR

    The VDR on-premises component was deployed as a Virtual Appliance into the same VMware cluster where the VMS and CV workloads were running. The VM specifications we used for the VDR virtual appliance are:

    • 4 x CPU
    • 8 GB Memory

    • 48 GB Disk

    Throughout the complete duration of our testing, the maximum CPU utilization of the VDR appliance was <10% of the allocated 4 vCPU cycles. Our largest test configuration required VDR to simultaneously manage scans of 79 total servers and devices. We believe that the VDR appliance CPU utilization scales approximately linearly as the device counts increase and therefore expect that the VM resources specified above could handle hundreds more devices.


    XDR


    Collector deployment

    One of the two ways to deploy XDR is by configuring an XDR Collector virtual appliance that will forward logs to the Secureworks cloud service for analysis. For our initial round of testing, we deployed an XDR virtual appliance onto the same VMware cluster where the VMS, CV, and VDR resources were hosted. The virtual appliance was easy to install and works well in a virtualized environment. The VM specifications we used for the XDR virtual appliance are:

    • 4 x CPU

    • 8 GB Memory

    • 20 GB Disk


    Red Cloak

    Our second set of tests were focused on changing from the Collector to the Red Cloak agent. The details of the Red Cloak installation are located at https://docs.ctpx.secureworks.com/integration/connectEndpoint/red_cloak_endpoint_agent_install/.

    These need to be reviewed for details on specific ports that may need to be opened in a firewall. The Red Cloak agent also is Proxy aware. So, if an internal Proxy server is available then that would be a preferred option compared with opening ports for each server that requires Red Cloak protection.

    Best practices

    Our lab testing produced many best practices that can be leveraged by anyone wanting to perform a similar proof-of-concept as follows:

    • Ensure that all Windows and Linux operating systems are fully patched and updated before scanning. Failure to do so will expose many vulnerabilities and create unnecessary noise in your dashboard reporting.
    • Do not use weak or common passwords on devices (servers, switches, cameras, and so forth). These are easy targets for unauthorized access to systems and will immediately be flagged.
    • IP cameras are frequently left unpatched for long periods after being deployed. Be sure to ensure they are patched to the latest versions per the vendor and included in your scanning efforts.
    • If vulnerabilities still exist after patching to the latest software and firmware, then reach out to your vendor for clarification as they may not be aware of the vulnerability, or may have a more recent update.
    • Do not assume you are safe after the initial scanning and remediation. Perform regular scans on your infrastructure. The Secureworks threat library for VDR hosted in AWS is constantly being updated and will continue to expose new vulnerabilities on your system when they emerge.
    • It is also recommended to consult with Secureworks because they have many offerings including managed services that will help you remediate your environment.