Database Security Checklist for Small Teams
Cover accounts, network exposure, encryption and logging.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a database security checklist for [DATABASE_AND_HOSTING]. Who accesses it: [ACCESS_GROUPS]. Sensitive data held: [SENSITIVE_DATA]. Current practices: [CURRENT_PRACTICES]. Cover least-privilege accounts, no shared logins, strong authentication, no public network exposure, encrypted connections and storage, secrets kept out of code, patching, audit logging, backups protected, and removal of access when people leave. Return a table with Check, Why it matters, How to verify and Status, ordered by risk. This is a defensive review of systems I own. Include a short plan for the first week and a quarterly review. Legal duties for personal data and breaches are [VERIFY] for [JURISDICTION]. Provide a ten-minute self-audit for a team lead who is not a database specialist, with yes or no questions, and an escalation path to an expert for any no. Add a short section on logging: which events to log, how long to keep logs and who reviews them. Remind the team to test restoration of encrypted backups and to store keys separately from the data they protect.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.