Quick Links
Helpful Links
Filtering and Audit Logging Solutions
ChallengeControl over processing directives, how traffic gets routed and whether or not external systems should be allowed to have access to data, are the primary concerns of any security policy. Ensuring that the flow of data is adequately filtered so that unwanted behaviors are avoided is critical.
All access and interactions with your systems should be logged so that they can be audited in the case of a security incident.
Solution
Symlabs Virtual Directory Server and LDAP Proxy are built around a tightly integrated condition model, where each behavior of the system is triggered based on particular conditions being met. This system allows you to define a variety of very particular conditions that control whether or not a processing directive will be triggered or not. Furthermore, traffic can be stopped or rerouted based on a range of possible triggers. For, instance filters within the system allow you to control the behavior of the system based on the source IP address or network from which a request was sent; the Base DN that the request is directed to, the BIND DN that was used to authenticate the user of the request, or even on customized conditional statements.
Plugins to reroute traffic to particular backend servers, based on information within the request PDU (such as the filter used in a search request, or the suffix of a request) are also available to further enhance control over traffic flow.
Each built-in component or plugin used within the system provides its own logging capability so that it is possible to completely monitor the functioning of the system itself and watch for malicious activities.
Finally, a wide variety of audit logging plugins are also available to extract information from within packets of data that traverse the system and write relevant information to a log file. These audit logging plugins can be used to track the interactions between client applications and backend systems.