Detection of child sexual abuse material on work computers and in cloud storage
Detects CSAM based on law enforcement classifications
Real-time detection and response
Effortless and operates discreetly in the background
Minimal impact on device performance
Detects on file level using advanced hashing technology
Always on – online and offline
The ProActive agent runs in the background monitoring file changes.
An incident is reported by an agent when a user handles a CSAM classified file.
The appointed incident manager receives a notification and can access all incident information via the ProActive Management interface.
Incident information such as time of incident, file and computer name can be extracted in multiple formats and used for further investigation.
The information can also be integrated with other security platforms for even more in-depth investigations.
Find out more about our products and how they fit into your existing IT protection.Get in touch
Police seize images and video
Police verify and classify files as CSAM
A unique digital signature is retrieved for each file
These signatures are continually added to the ProActive Signature Database
All agents use a local copy of the signatures for comparison and detection
Integrate NetClean ProActive with your existing security or SIEM system. With the webhook add-on, you can also gather more comprehensive data from other security solutions in your system, allowing you to get a broader picture of the user and asset that triggered the incident.
This extended data enables you to conduct more thorough investigations, both internally and in cooperation with law enforcement.
VMware Carbon Black Cloud
VMware Carbon Black Cloud is a cloud native platform that provides anti-virus and endpoint detection and response, threat hunting and vulnerability management.
Integrating VMware Carbon Black Cloud with ProActive enables more thorough investigations when CSAM is detected on an endpoint. Carbon Black Cloud is capable of providing additional relevant information, such as extended data and analysis of both the user and endpoint that triggered the incident.
Frequently answered questions