- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Hello everyone,
After upgrading gateway to R80.10 we noticed rules with Application/Service set to Any do not log applications that match the rules. The exact same rules with R77.30 gateway and R80.10 SMS work fine.
We have tried with both shared and separate layers for network and application rules.
We have tried all kinds of tracking and logging, but the result is always the same.
What am I missing?
What is your clean-up rule in Application ordered layer? That should be set to Accept and I recommend a Detailed logging with it's default configuration of Accounting and per Connection enabled:
This should log all traffic and applications if there are no other issues.
Obviously, the gateway handling this ordered policy needs to also have Application Control and URLF blades enabled.
Once you've established that you are logging what you need, unchecking the "per Connection" field will reduce the logs by not explicitly logging the Firewall established connections.
Also ensure that you don't have the Application ordered layer defaulting to an implicit Clean-up rule with drop, which is the default for new layers.
"Any" doesn't require the use of Application Control in order to validate.
The log entries you see will therefore show as being accepted by the Firewall and won't have the Application information in it.
The information is still there, but you have to drill into the log entry to find it.
See the following example:
I do not get this information.
In the Session tab, Blade is always Firewall.
Application/Site section does not show.
SmartEvent shows only YouTube in Accepted Applications list because there is an specific rule accepting it.
I will open an SR, but I believe the problem is in my understanding rather than an issue with my gateway.
In my case, my App Control rule is actually in a sub-policy:
I missed the detailed logging option. Thank you, Dameon!
What is your clean-up rule in Application ordered layer? That should be set to Accept and I recommend a Detailed logging with it's default configuration of Accounting and per Connection enabled:
This should log all traffic and applications if there are no other issues.
Obviously, the gateway handling this ordered policy needs to also have Application Control and URLF blades enabled.
Once you've established that you are logging what you need, unchecking the "per Connection" field will reduce the logs by not explicitly logging the Firewall established connections.
Also ensure that you don't have the Application ordered layer defaulting to an implicit Clean-up rule with drop, which is the default for new layers.
Detailed logging did the trick! I had only Accounting enabled.
I opened that windows a thousand times and didn't see that. My colleagues neither.
Thank you, Eric!
Hi @Eric_Beasley ,
If I put services in a specific rule, will the firewall be able to log the relevant application?
I'm just trying to create new rule set from R77.30 to R80.30 but in this phase of the migration I prefer to leave the configured rule exactly the same and in a second phase to change them with relevant app.
How can I accomplish this? (obviously I cannot put any in the service/app column field and obv the ordered layer will have apcl enabled).
Let me know guys if you have any suggestion/tips.
D!Z
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY