Securly Default Policy overriding Custom Policies

[altecsole]

I've logged a support ticket with Securly, but interested to know if this is happening for anyone else?

 

Our Default Policy seems to be overring custom policies. For example, our Default Policy has the E-commerce/Shopping category set to Blocked, but this Category is allowed for Staff. However, when trying to access shopping sites, such as amazon.co.uk, Securly is blocking staff due to E-Commerce/Shopping. The Activities logs shows that the users are being assigned the correct policy, but then the Default Policy kicks in and blocks. I've tried adding amazon.co.uk and *.amazon.co.uk to the policy allow URL list, but still the same. 

[TronXP]

If Securly is having issues,  it defaults back to a "safe" filter and ignores all your custom policies.  We are having some weird things with securly this morning, so maybe there is an issue.

[StephenPink]

Yes - we've got the same at several sites, and have a ticket with Securly. Seems to be related to an update yesterday - no details from them yet.

Shame as recently there have been a number of disappointing incidents with Securly.

[chrisgreenwood]

[altecsole]

Thanks. Seems to be back to normal for us.

[chrisgreenwood]

8 minutes ago, altecsole said:

Thanks. Seems to be back to normal for us.

 

Ye we should be fine for a few weeks now 😂

[StephenPink]

Yep all seems fixed now. Only details that were shared to us was "It seems there was an update released overnight which was the cause of the issue. We are working on rolling that back ASAP to resolve the issue."

Not the first update in recent times that's caused disruption unfortunately. 

[NKPaul]

I've got something like it now.

Member of staff can't access amazon music, the activity shows him allowed by the staff policy then blocked by the default policy.

 

[altecsole]

58 minutes ago, NKPaul said:

I've got something like it now.

Member of staff can't access amazon music, the activity shows him allowed by the staff policy then blocked by the default policy.

 

We don't seem to be experiencing any issue as the moment - touch wood!

[e-class]

Ah so that explains it. I had exactly that issue, had a to and fro with the Securly engineer, but didn't get to the bottom of it, then suddenly it started working. No idea why he didn't say this is currently a global Securly issue!

Edited May 23 by e-class