A cloud provider’s safeguards do not answer every question about your identities, data or application settings. Responsibilities vary with the service model and the way the organisation uses it. An assessment should follow the actual workload and its dependencies rather than assume one division of responsibility across every subscription.
We help define a review that connects business use with technical evidence. The useful question is not simply whether a setting differs from a benchmark. It is what the setting permits, who relies on it, what could be affected and whether the organisation has deliberately accepted the trade-off.
Architecture review and testing have different scopes. Configuration and evidence review can identify important weaknesses without attempting exploitation. If penetration testing or intrusive validation is needed, define it explicitly with authorisation, provider conditions and safe test boundaries. A cloud assessment does not automatically include testing third-party infrastructure.