Spotify block through override not taking effect

Forum|Forum|6 years ago
June 20, 2019
3 replies
23657 views

I'm having an odd issue with Application Control (Blocking Spotify) on an outgoing client policy on 6.2. Wondering if anyone would have any insight to what I may be missing?

The application control profile has Spotify added as an override with Block as the action. When I check the logs and filter Spotify it appears with pass as the action.

I've confirmed through these records that it is the correct policy which has the profile with the override in it that is being applied to that traffic.

Is there anything else in the app control profile that needs to be done other than adding the override block in order for that to work?

Screenshots linked below. Thanks.

https://www.dropbox.com/s/nomrodlithgsvnf/spotify1.PNG?dl=0

https://www.dropbox.com/s/1mlqf5g15kddmgi/spotify2.PNG?dl=0

https://www.dropbox.com/s/d0s0arkt5e4qeod/spotify3.PNG?dl=0

https://www.dropbox.com/s/hjgz9ml98ipzerb/spotify4.PNG?dl=0

6.2

hubertzw

New Member

Can you see in the logs the correct profile name (Application Control)?

jesse_fletcherAuthor

New Member

It appears that the Application Control Sensor appearing under the log details is "default" which doesn't match the "default-block-spotify" profile which has been created. Any reason why this profile would be showing even though the other is assigned to the policy which the traffic is passing through? The correct policy #27 is showing in the log detials which has the "default-block-spotify" profile attached. Screenshots below.

https://www.dropbox.com/s/uqsgy5q12kwkl0p/spotify5.PNG?dl=0

https://www.dropbox.com/s/v7g4q3h27o5yjxq/spotify6.PNG?dl=0