Velosecure's decision branching is powered by the SocratesEngine. Rather than simply dumping every single file or registry key, Velosecure determines a machine's role in your business infrastructure. Based on its role, the type of Windows version, how it was installed, and how it is configured, different information is collected and assessed.

In the example from the Velosecure Product News page, if your Windows server was determined to be an Exchange Mail server on Windows 2003 Server, Exchange specific registry keys would be probed and the Exchange directories would be passed to the directory permissions module for parsing. So based on the Exchange services, the application directory would be retrieved and permissions for that directory would be reported. Additionally, the registry keys for sensitive Exchange settings would also be obtained, as well as the important registry values. Based on those settings, additional parameters might be sent to the directory permissions module or Auditing. The idea is that all laborious manual cross references of data is eliminated.

It would take many web pages to explicate all the decision relationships within Velosecure, but to give a high level understanding the following flow diagram depicts the concept. If you have additional questions please contact us.