Trusted Network Share - How to handle when accessing via web browser vs. Windows File Explorer?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Trusted Network Share - How to handle when accessing via web browser vs. Windows File Explorer?

L4 Transporter

We have a few Trusted Network Share policies that trust any applications copied from or installed from the shares. The trust is based on the source being in the below format:

 

\\<sharename>\<foldername>

 

This works great when people get the applications from there using Windows File Explorer. But we noticed that more and more people are now using their web browser (e.g. Chrome) to navigate to that share and get the applications. This then causes the source to look like:

 

file://<sharename>/<foldername>

 

And because of this, the policy doesn't match, even though the app came from the trusted network share.

 

Other than creating a second policy for the second format of the source, is there a good way to handle this? Can something be done within the original policy to allow for both formats?

4 REPLIES 4

L2 Linker

Hi Ron,

 

Having a second policy for the second format would be your best choice in this scenario. Can you also share a screenshot of what you have within that original policy now?

 

Thank you,

Sandra

Hi Sandra,

 

It's a specific network share using the format of \\<sharename>\<foldername>. For the scope it allows all the application types, child processes, and installed applications (elevate if necessary). A typical trust policy.

 

Thanks!

L5 Sessionator

Hi @Ron Martin​,

 

  • When a file is being downloaded from the share by browser, its source has a type of internet
  • The second mentioned policy should be created but it needs to target the URL
    • When targeting source URLs, you must provide a publisher name (internal condole validation), and any publisher can be provided.

 

For example:Field_Content_versions_oct20__0682J00000OvfKrQAJ.png 

Note: You can have one policy with two targets or two different policies.

 

Thanks,

Tamir

Thanks {@0052J000009Skt5QAC}? , that makes sense. Unfortunately that means it won't work for us then. We have a lot of applications (primarily open source) that are not signed (7-Zip is a great example), so there is no way to use the publisher's signature property (any signature won't work since there is NO signature). This is why I have the ER - Do NOT require publisher signature for source URL policy (force.com) open and hope it gets implemented in the near future (please upvote it).

 

You mention that you "can have one policy with two targets". How do you do that? There doesn't seem to be a way of doing "this target OR that target". From my understanding it's always an "AND" boolean. Publisher signatures can be separated by semicolons, but I don't think the other properties can.

 

Thanks again for your answer.

  • 11 Views
  • 4 replies
  • 0 Likes
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!