Can I use a wildcard in an FQDN object?

cancel
Showing results for 
Search instead for 
Did you mean: 

Can I use a wildcard in an FQDN object?

L2 Linker

Having an issue logging into an online marketing screen tool called screencloud.  The browser throws a CORS error once they hit login and the web application throws Unexpected_API_Result.

 

The only way for our marketing staff to sign into this specific service is to use their personal device or cell phone.  Any company equipment either on site or on global protect will not allow them to log in.


I'm thinking its the decryption policy.  I want to put a negate for an object group that contains all of the FQDNs that the company has provided.  They are saying this is the list below, but I'm really thinking its not possible to use a wildcard character is it?

 

What are the domains & servers I need to whitelist?

Here is the full list of servers/domains you need to whitelist:

*.screen.cloud

*.screencloud.com

*.firebase.com

*.googleapis.com

*.gstatic.com

*.s3.amazonaws.com

*.cloudfront.net

*.screencloudapp.com

*.imgix.net

*.sentry.io

*.screencloudapps.com

*.api.filepicker.io

*.assets.filepicker.io

*.filepicker.io

*.datadoghq.com

*.filestackapi.com

Also, the ports we use are 80 and 443

1 ACCEPTED SOLUTION

Accepted Solutions

L4 Transporter

You can not use wildcard FQDN address objects because the PA must resolve the IPs to be able to apply them in a rule.

 

However, you can create wildcard URL objects to match paths in the decryption rules:

Objects->Custom Objects->URL Category->[DND-URLs]

    example.com/

    *.example.com/

Policies->Decryption->[Do-Not-Decrypt-My-Dest]

    src-zone=Trusted, dst-zone=Untrusted, url-category=[DND-URLs], action=no-decrypt

View solution in original post

2 REPLIES 2

L4 Transporter

You can not use wildcard FQDN address objects because the PA must resolve the IPs to be able to apply them in a rule.

 

However, you can create wildcard URL objects to match paths in the decryption rules:

Objects->Custom Objects->URL Category->[DND-URLs]

    example.com/

    *.example.com/

Policies->Decryption->[Do-Not-Decrypt-My-Dest]

    src-zone=Trusted, dst-zone=Untrusted, url-category=[DND-URLs], action=no-decrypt

Ah great idea!  I created a new decryption policy above our current one set to no-decrypt for a new URL Category.  That seems to work!

 

Thanks, I'll mark that as a solution!

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!