DNS names missing/incorrect about cloudappsecuritydocs HOT 5 CLOSED

Hi @mschultz-bcbsne thanks so much for your feedback. I'm sorry it's taking so long to get an answer about this, but I'll update you as soon as I get confirmation and update the page.

from cloudappsecuritydocs.

Hi @mschultz-bcbsne The list focuses on the items you need to configure on your firewall to enable connection from Cloud App Security. In the case of this proxy, this is an outgoing connection which usually doesn't require any specific configuration. hope that helps, thanks, Rachel

from cloudappsecuritydocs.

#please-close

from cloudappsecuritydocs.

@msmbaldwin

from cloudappsecuritydocs.

Then I guess I need to change my comment. The intro to the article doesn't specifically say it's for allowing inbound connections:

This article provides a list of ports and IP addresses you need to allow and white list to work with Microsoft Cloud App Security.

And the Portal Access section is even specifically about outbound connections. I understand it focuses on connections to the portal, not applications protected by the MCAS proxy feature, so perhaps that verbiage needs to be updated, or an additional section needs to be added.

I understand the proxy is an outbound connection that usually doesn't require any specific configuration, but for many enterprises (mine included) that's not the case. We did need to make certain configuration changes to HTTPS inspection and other outbound security measures, and it was specifically the *.cas.ms addresses not listed in this article that were the problem. It is extremely helpful to have the full list of URLs the service may use so that customers don't have to go back and forth with other internal teams. Lots of "oh, now it looks like it needs these addresses" over the course of tickets and other red tape makes implementation very frustrating.

Please reconsider adding the information before closing this issue.

from cloudappsecuritydocs.