Create and Edit Access Control Rules
If you edit an access control rule that is actively in use, the changes do not apply to established connections at deploy-time. The updated rule is used to match against future connections. However, if the system is actively inspecting a connection (for example, with an intrusion policy), it will apply changed matching or action criteria to existing connections.
For FTD, you can ensure that your changes apply to all current connections by using the FTD clear conn CLI command to end established connections. Note that you should only do this if it is acceptable to end those connections, on the assumption that the sources for the connections will then attempt to reestablish the connection and thus be matched appropriately against the new rule.
Procedure
Step 1 | In the access control policy editor, you have the following options:
If View () appears next to a rule instead, the rule belongs to an ancestor policy, or you do not have permission to modify the rule. | ||
Step 2 | If this is a new rule, enter a Name. | ||
Step 3 | Configure the rule components. If you are bulk-editing multiple rules, only a subset of options are available.
| ||
Step 4 | Click OK to save the rule. | ||
Step 5 | Click Save to save the policy. |
What to do next
If you will deploy time-based rules, specify the time zone of the device to which the policy is assigned. See Configure Device Time Zone for Policy Application.
Deploy configuration changes; see Deploy Configuration Changes.