As of 13 August 2026, AI can only partly secure cloud storage for your business.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open the administration console for your cloud-storage provider and record the provider, product, users, groups, administrator accounts and storage locations without copying any passwords, tokens or private keys.
   2. Gather the provider's current documentation for MFA, roles, external sharing, public access, encryption, audit logs, alerts, backups, retention and recovery, then redact personal data and secrets from any configuration export or screenshots.
   3. Paste the environment summary, redacted settings and relevant documentation into an AI chat using the supplied prompt, and ask it to separate confirmed settings from assumptions.
   4. Compare every proposed setting with the provider's current documentation and mark recommendations that are provider-specific, uncertain or unsupported before accepting any change.
   5. Create a non-production test location, apply one approved change at a time, and test normal user access, blocked unauthorised access, external sharing restrictions, logging and recovery without deleting production data.
   6. Have a technically competent colleague compare the change list with the test results and approve the production sequence, rollback steps and evidence to retain.
   7. Apply the approved changes in the administration console, then save dated evidence of the settings, alerts, access tests and a successful recovery test.

   Prompt

   Act as a cautious cloud-security review assistant. Help me secure my business cloud storage without making changes or claiming that a setting is safe unless the evidence supports it.
   
   Environment:
   - Storage provider and product: [provider and product]
   - Business size and user roles: [details]
   - Data stored: [types of data, with no personal data, passwords, access tokens or private keys]
   - Current sharing model: [details]
   - Current identity and access controls: [details]
   - Current encryption, logging, alerting and backup settings: [details]
   - Relevant business requirements: [retention, recovery, customer access, UK GDPR or contractual requirements]
   - Redacted configuration or screenshots: [paste here]
   
   Produce:
   1. A short list of the most serious risks, separating confirmed facts from assumptions.
   2. A prioritised remediation plan covering administrator access, MFA, least privilege, external sharing, public access, encryption, logging and alerts, malware protection, backups, retention, deletion and recovery testing.
   3. Exact settings or commands only when they are specific to the named provider and product. Otherwise say that I must check the provider's current documentation.
   4. A safe test plan that does not delete data or interrupt users.
   5. A rollback plan for each proposed change.
   6. A list of evidence I should collect before declaring the storage secure.
   
   Do not ask me to paste secrets or personal data. Do not invent provider features, compliance claims or configuration values. Flag anything that needs a cloud-security professional to review. End with the three checks I should complete before changing production settings.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.