What is our primary use case?
My main use case for Microsoft Defender for Cloud Apps is that it is our primary CASB solution. We use it to protect any kind of access, as we enforce data controls on sessions that are initiated on desktops and endpoints we do not manage. If employees need to access any corporate application, they are able to access it from their own personal devices, but we use this product to enforce security restrictions within that session. For example, users cannot copy or download content from there. They can work inside that session, but they cannot take content out of it.
How has it helped my organization?
Session controls benefit our organization because they meet, or help meet, the data control standards we have within the organization, and they help us extend data controls to devices which we do not manage.
The impact on our ability to assess and manage app-related risks is that Microsoft Defender for Cloud Apps definitely gives us good insights to make decisions about whether to allow or block a particular application. Over time, it also helps us see the adoption rate. If an app is not being used, we can reduce it, and we save some licenses around that.
What is most valuable?
The feature of Microsoft Defender for Cloud Apps that I appreciate the most is session controls.
We use the visibility into OAuth apps provided by Microsoft Defender for Cloud Apps often. We use the app governance functionality within Microsoft Defender for Cloud Apps pretty often to understand which applications are overprivileged and overpermissioned, and which apps are stale, have not been used, and are still added in our organization registry. We use that pretty often to clean up any kind of old apps.
We also use Microsoft Defender for Cloud Apps for visibility into and risk management of our generative AI apps. We have onboarded our devices to Defender for Endpoint, and that sends the network traffic to Microsoft Defender for Cloud Apps. Microsoft Defender for Cloud Apps parses that information and provides visibility into which generative AI apps are being used, which are approved by IT, and which are not approved by IT, so we get better control from there.
The integration of Microsoft Defender for Cloud Apps with Microsoft Defender XDR at defending against SaaS attacks is pretty good where it is right now. The correlation brings us insights into an incident, as it can correlate alerts from Defender for Office and Defender for Endpoint with telemetry coming from Microsoft Defender for Cloud Apps, and that is very valuable for understanding what has happened when an incident has occurred. It helps us understand what the attacker did once he was inside, once he compromised the account, what he did with the data, and where the exfiltration was happening. All that insight is given by Microsoft Defender for Cloud Apps, and tying that data with XDR gives us the full context around the incident. It really helps.
What needs improvement?
Microsoft Defender for Cloud Apps can be improved through closer ties to Global Secure Access. Microsoft has a product called Global Secure Access, and a tight integration between it and Cloud App Security on use cases that go beyond the current one would help. Examples include managing or creating inline DLP policies, which would be on the network, even for applications which may not be managed by organizations. For instance, if a user is using a personal OneDrive or a personal Gmail, I want to block that, but I want to allow the corporate side of that application. That is lacking.
One feature I want to see in a future release of Microsoft Defender for Cloud Apps is the ability to distinguish and block apps which are personal and corporate. For an application which has both versions, we would have a capability to block the personal one and allow the corporate one.
For how long have I used the solution?
I have been using Microsoft Defender for Cloud Apps for 10 years.
What do I think about the stability of the solution?
Microsoft Defender for Cloud Apps is pretty much stable. I have not seen any incidents of instability on the product yet.
What do I think about the scalability of the solution?
Microsoft Defender for Cloud Apps scales very easily with the growing needs of our organization, I think, because once we have deployed the policies, it is rinse and repeat, adding people to those groups so that they get the policies. We have not had any issues with scaling until now. We have deployed it for customers who have 17,000 users, 20,000 users, and 60,000 users, and I have not seen any problems. Once we have the baseline fundamentals set, it is just a matter of adding users into that policy, and that is all it takes.
Expanding usage of Microsoft Defender for Cloud Apps has been smooth as long as the work is done beforehand, where you have designed your policies well and tuned them enough so that you can scale them out to all production users and know what the impact would be. The initial work is a little bit more. Once you do that, I think the scale becomes easy.
How are customer service and support?
On a scale of 1 to 10, I would rate customer service and technical support for Microsoft Defender for Cloud Apps as follows. The product overall would be 8.5, and the service, which is the customer support service, would be a seven.
Which solution did I use previously and why did I switch?
Prior to adopting Microsoft Defender for Cloud Apps, we were not using another solution.
How was the initial setup?
My experience deploying Microsoft Defender for Cloud Apps is that we have deployed it internally, and we have deployed it for other customers also. The experience has been that it is not that complicated. There are certain use cases which really stick with customers and with us, such as Shadow AI application, app governance, and session controls. These are three key features which we see customers adopting and deploying. Using Microsoft's inbuilt policy templates makes the rollout pretty easy.
What was our ROI?
We have seen return on investment with Microsoft Defender for Cloud Apps, and there is definitely value. As I mentioned, those three key features, Shadow AI discovery and session controls, have helped us enforce our data security strategy across our device estate. We definitely have an ROI, because if we did not have that, I do not know what else we would use. It is good protection.
Which other solutions did I evaluate?
Other solutions we considered before selecting Microsoft Defender for Cloud Apps include maybe Netskope.
What stands out to me in the evaluation process is that we incline towards Microsoft's solution because most of our stack is on Microsoft, and our security solutions are in line with what Microsoft is offering. Microsoft Defender for Cloud Apps closely aligns with the vision we have from a longer-term standpoint. That is why we chose it, basically because of the integration with Microsoft.
What other advice do I have?
Overall, on a scale of 1 to 10, I would rate Microsoft Defender for Cloud Apps definitely 8.5 to nine.
My advice for other organizations considering Microsoft Defender for Cloud Apps is definitely to give it a shot, especially if you are in the Microsoft ecosystem and you have devices onboarded to Defender for Endpoint. In today's world of AI, Microsoft Defender for Cloud Apps gives good telemetry about your Shadow AI space. That space is growing, and we know it will be a problem going forward. Give it a try, see what data is coming out from your enterprise, and then make a decision.