I'm with Tom in that I prefer a written Security Policy and the implied threat of punitive action, rather than trying to engineer a technical fix to prevent Local Admins from bypassing security.
In my experience, there must be a buy-in from Top Management for any security system to work
effectively. In the case of CSA they must be willing to pick up the phone and call people who shut down CSA without a documented reason.
Managers will have all the proof they need by a quick glance at the Events Log to make these calls. This paper trail will keep them from being accused of harassment and if the employee continues violating the security policy will give them the grounds for termination.
In sum, let the CSA do what it does best, namely, protect assets and let management enforce the penalties for violations of policy.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...