- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hello,
We have a App based rule for Webex but it seems to be allowing traffic for Amazon instances as well.
Could you please confirm how this is happening.
Although the user states that the Amazon instance is not reachable but still allow logs can be seen as attached.
Is it the service/port that has matched and and hence the allow logs? But then app based rule should allow only the application mentioned in the policy.
Also note that we have a rule in https inspections that with Destination- Webex services and Action-Bypass.
Is this causing the application to not being identified correctly and hence we see the allow logs for Amazon.
Just FYI that the application blade licenses are valid.
Thanks in advance for any suggestions on this.
Consider using the Updatable Object for WebEx.
From the Updatable Object see the link to Network Requirements for Webex Services:
https://help.webex.com/en-us/article/WBX000028782/Network-Requirements-for-Webex-Services#id_135011
It states the following:
Cisco supports Webex media services in secure Cisco, Amazon Web Services (AWS) and Microsoft Azure data centers. Amazon and Microsoft have reserved their IP subnets for Cisco’s sole use, and media services located in these subnets are secured within AWS virtual private cloud and Microsoft Azure virtual network instances. The virtual networks in the Microsoft Azure cloud are used to host servers for Microsoft’s Cloud Video Interop (CVI) service.
So perhaps this is the reason connections to Webex also contain traffic for AWS.
Here are few of the IP addresses for Amazon which we have in the logs are 52.48.220.40, 52.209.105.52, 54.77.215.5, 52.213.104.140 and 52.18.36.25 and these are not present in the link which you have mentioned.
What is the precise rule the traffic matches on?In any case, what you see in SmartView is the reverse DNS lookup of the IP, which in this case indicates it’s in AWS.
Which, if the company is hosting the specific service in question there, is expected behavior.
Hello,
Can you show a detailed log for one of those sessions ?
Than you,
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 19 | |
| 17 | |
| 14 | |
| 8 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY