Name → HTTP-HTTPS-QoS

Apply QoS On → Interfaces in Destination Interface Objects

Download/Upload Limit → 5 Mb/s

Source Interface Networks → 192.168.1.0/24

Destination Interface Networks → 192.168.2.0/24

Destination Ports → HTTP-HTTPS

The HR workstation resides on the inside 192.168.1.0/24 network, making that subnet the source-interface network. Internet-bound traffic exits through the 192.168.2.0/24 network, which must be configured as the destination-interface network. Because rate limiting must occur as traffic leaves toward the internet, QoS is applied to interfaces in the destination interface objects. The HTTP-HTTPS object identifies the destination ports for web traffic, while HTTP-HTTPS-QoS provides a descriptive rule name. Both download and upload limits are configured as 5 Mb/s. Cisco Secure Firewall applies a QoS limit independently on each selected interface and determines upload and download direction based on the connection initiator. The Apply QoS On selection must correspond to a populated source or destination interface condition. Cisco Secure Firewall QoS configuration

In Cisco Secure Firewall Management Center (FMC), when two users attempt to modify a VPN policy simultaneously, the system implements a locking mechanism to prevent conflicts. The first user who selects edit on the policy locks the configuration, preventing other users from making changes until the lock is released.

Steps:

When the first user selects edit on the VPN policy, FMC locks the policy for editing.

The lock ensures that only the first user can make changes.

Once the first user saves or cancels their changes, the lock is released.

Other users can then edit the policy.

This locking mechanism ensures that configuration conflicts are avoided and only one set of changes is applied at a time.

Change Reconciliation is specifically designed to generate and email a detailed summary of configuration changes made during the preceding 24 hours. Secure Firewall Management Center takes snapshots when users save configuration changes and consolidates those records into a daily change report. The administrator can enable the feature, select the scheduled delivery time, specify recipient email addresses, and optionally include the full change history. Sending audit logs to a syslog or HTTP server exports individual audit events to an external system but does not automatically generate the required daily management report. STIG Compliance evaluates the system against security configuration guidance and is unrelated to change reporting. Therefore, Change Reconciliation is the only option that directly satisfies both the 24-hour reporting period and email-delivery requirements. Cisco Change Reconciliation configuration

================