02-13-2017 08:15 AM
Issue background:
We have a policy for Application Whitelist of allowed applications on the internet firewall. SourceForge-Base is one of these applications. SourceForge-Base had dependencies on SSL, Web-Browsing, and SSH. We allow SSL and Web-Browsing, but do not wish to allow SSH to the entire outbound internet. Our users traffic works fine with only SSL and Web-Browsing being allowed in conjunction with SourceForge-Base when they access SourceForge.
Without knowing the IP ranges utilized by SourceForge to allow that in a separate policy by service port, (also without utilizing SSL decryption so an FQDN is not an option), we have no way to allow the traffic other than by application.
Is there a way to hide or suppress persistent application dependency warnings in specific so that a commit can come back without warnings?
Or is there a way to allow SSH only if it is used in conjunction with SourceForge-Base, as in SSH being an Implicit Use Application for SourceForge-Base?
