The Agent Service Control (ACS) rule can control whether administrators are allowed to stop agent security. This is through a net stop command on Microsoft Windows or through /etc/init.d/ciscosec stop on UNIX, and end users can disable security through the agent UI security slide bar. If you stop the agent security, this disables all rules until security is manually resumed or the system is rebooted.
If you use this rule in order to deny agent service stops, the agent service cannot be stopped on the system in question and therefore agents cannot be uninstalled.
Complete these steps in order to add these rules to your module:
Choose Add Rule at the bottom of the rule list. A pop-up list of the available rule types appears.
Choose the Agent Service Control Rule. This takes you to the configuration view for this rule type.
In the Agent Service Control rule configuration view, enter this information:
Description—Enter a description of this rule. This description appears in the list view for the module. Optionally, expand the +Detailed field in order to enter a longer description.
Enabled—Use this checkbox in order to enable this rule within the module. It is enabled by default. If you do not select this checkbox, you can save this rule, but it is not active in the module and it is not distributed to groups.
Complete this action and note that not all action types are available for this rule on Windows platforms.
Log—Enable this checkbox in order to turn logging on for this rule. Generally, you want to turn logging on for all deny rules. This means that the denied system action in question is logged and sent to the server at regular time intervals.
Take precedence over other rules—Enable this checkbox in order to manipulate rule precedence so that this rule is evaluated before other similar rules. You should generally not require this checkbox. Do not use it without the comprehension of how it works. Refer to the Rules: Manipulating Precedence section of Rule Module Configuration for more information.
Applications in any of these selected classes
Choose one or more preconfigured application classes. Note that the entry is selected by default. You can use this default or you can unselect it and create your own application classes. Refer to Using Application Classes for more information and application class configuration details. Note: On UNIX systems, anyone with root access can stop the agent service. IN order to prevent this, while you still allow administrators to stop the agent service, you need to configure an Agent Service Control rule in order to Deny from stopping the service. Then configure another Agent Service Control rule which Allows only a UNIX Secured Management application class to stop the service.
But not in the following class—Optionally, select application classes here in order to exclude from the application class(es) that you have selected in the included applications field. Note that the entry is selected by default.
Attempt to disable agent security
This checkbox controls whether users with administrator privileges can stop the agent service from the Service Control Manager or if thenet stop "Cisco Security Agent" is run from a command prompt on Windows or through /etc/init.d/ciscosec stop on UNIX.
Note This also controls whether the Off setting on the agent security level slidebar allows the end user to turn agent security off. If you do not allow the stopping of the agent service, the Off level, if available, is ineffective. Refer to the Agent UI Control section of Available Rule Types for more information.
Attempt to modify local agent configuration
The Cisco Security Agent has built-in global security policies, which protect agent binaries and data. Note that this protection is only offered when the agent service is running and is not stopped or in Test Mode. While you cannot turn these non-logged, built-in rules off while the agent is active, you can use this rule in order to monitor, terminate, or tag a process that attempts to modify the agent configuration.
Refer to Available Rule Types for more information and additional rules in order to control a different set of system resources.
Hey all, I'm working on a lab in PT and I'm wondering if someone could help me with the syntax for these two commands I need to put on my ASA:Put commands on ASA to allow for ASDM access from inside networkConfigure dynamic PAT using outside interface so ...
Greetings, Due to a bug I have to reformat my ISE units and reinstall. We are going to ISE 2.6. We have SNS-3595's. I believe 2.3 only took about 30-45 min, but 2.6 is taking a lot longer. Anyone have an idea on time?
vpnAny suggestions. Just added a site to site IPSEC tunnel from Cisco ASA running ASDM to a SonicWALL. Successfully got the tunnel live. However cannot reach anything in the cisco network from the SonicWALL. Also there was an existing Cisco AnyConnect SSL...
Hi Experts,We are moving away from NAC Agent to Cisco AnyConnect.There is this weird behaviiour that we are seeing, the AnyConnect is running the posture check twice.Once, when its in limited access and checks if the endpoint is compliant or not, then rep...