LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and build resilience
Awards and Accolades
The most recognized cybersecurity leader
LevelBlue SpiderLabs
Elite global threat experts and intelligence
PGA of America Partnership
Cybersecurity at the championship level
Secure What's Next
Future-proof your organization
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Cybersecurity threat protection resources
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » Legacy Products » Secure Web Gateway » Security Policies » FAQ: Always click "Commit changes" after editing policy...

FAQ: Always click "Commit changes" after editing policy items

Expand / Collapse
Show/Hide Article Tools


  • Question
    Why are my latest policy changes not being applied to new transactions?

  • Answer
    After making any policy-related change (such as editing a rule or a list) in the management console, it is necessary to click the Commit changes button, as shown below.



    Clicking on Commit changes will push the configuration changes to all of the relevant system components, including the Scanning Server.  This is necessary for All in One units as well as distributed environments with a Policy Server and multiple Scanning Servers.

    Almost all changes made in the management console must be committed in order to make them active.  A few changes do not require a commit because only the Policy Server component needs to be aware of them.  Addtionally, changing an IP address in Settings -> Devices will initiate a commit operation automatically, so it is not necessary to click the Commit changes button.

    When there is any doubt, clicking the Commit changes button is recommended.  If there are no changes to commit, clicking the button will not cause any harm.  The system will simply warn the administrator that there are no changes to commit, as shown below.  Clicking the Cancel button will close the window.



    If the administrator clicks the button and there are pending changes, the system will list the modules that will be affected by the commit operation.  This is depicted in the screenshot that follows.  When the administrator clicks the OK button, the changes will be committed.  It may take a minute for the commit operation to complete.  It will be finished when all of the IPs in the Network Roles list (Settings -> Devices) have the same configuration revision.


  • Software Version
    8.3.X
    8.4.X
    8.5.0

    • This article was previously published as:
    Finjan KB 1578

    To contact LevelBlue about this article or to request support:

    Rate this Article:
         
    Tags:

    Add Your Comments


    Comment submission is disabled for anonymous users.
    Please send feedback to Trustwave Technical Support or the Webmaster    .


    Execution: 0.063. 8 queries. Compression Disabled.
    Powered by InstantKB.NET