Security checklist for Databases & Users

This article is part of the Spark Rack Databases knowledgebase and covers Databases & Users. This security checklist focuses on identity, authorization, credential handling, change evidence, recovery readiness, and safe communication with Spark Rack support.

The relevant customer area is Services > Databases or Control Panel > Databases. It is used to manage databases and database users, including full names, hosts, ports, credentials, assignments, privileges, application configuration, and credential rotation. Controls can differ by product, lifecycle status, account permission, domain state, payment method, or service configuration. When an action is not shown, confirm eligibility and permission instead of following an unrelated workaround.

Before you begin

• Create a verified database backup
• Know source and destination engine versions
• Record the full displayed database and user names
• Use a unique strong database password
• Schedule production imports or restores during a controlled window
• Identify the exact item associated with databases and database users and confirm its current status.
• Write down the expected result and the current value before changing anything.
• Plan a rollback or recovery path for any action that can affect access, billing, data, routing, delivery, or availability.

Security control checklist

• Use a unique password stored in a reputable password manager and enable two-factor authentication for every account user who can access it.
• Give each person an individual account user instead of sharing the owner login. Remove access promptly when responsibilities change.
• Do not send passwords, two-factor recovery codes, full payment-card data, private keys, API secrets, or unredacted identity documents in a normal support reply.
• Review unexpected sign-in notices, permission changes, domain changes, payment changes, and credential resets as possible security events.
• After an access-related incident, rotate affected credentials, review delegated users and contacts, verify domains and DNS, and document the recovery actions.
• Confirm the exact authorization boundary for databases and database users; the ability to view an item does not always imply permission to change every setting.
• Treat values related to full names, hosts, ports, credentials, assignments, privileges, application configuration, and credential rotation according to their sensitivity and operational impact.
• Use a clean, updated browser and verify the Spark Rack domain before signing in or entering payment or credential information.
• Preserve evidence of unauthorized or unexpected activity before deleting messages, resetting everything, or making broad changes.
• Maintain a tested recovery route that does not rely exclusively on the device, mailbox, domain, or credential currently at risk.

Response to suspected compromise

1. Use a known-clean device and network to secure the primary email account and password manager first.
2. Change the Spark Rack password and two-factor settings, and save new recovery information securely.
3. Review account users, contacts, payment methods, services, domains, DNS, mailboxes, credentials, and recent support conversations.
4. Revoke unknown access and rotate every secret that may have been viewed or reused.
5. Contact Spark Rack with the timeline and affected objects, without placing active secrets in the request.
6. Monitor the account and customer-facing services for recurrence.

Detailed operating procedure

Use this sequence as the baseline workflow for Databases & Users. Some steps may be informational when the selected product does not expose that exact control, but the verification and recordkeeping principles still apply.

1. Create the database and a separate user
2. Assign the user to the database with required privileges
3. Use the provided host and port rather than assuming localhost
4. Update the application with the full database name, username, host, and password
5. Inspect SQL dumps for character sets, definers, engines, and hard-coded names
6. Import using a method appropriate for file size and then run application migrations in order
7. Validate tables, row counts, encoding, and application read and write behavior
8. Confirm that dependent settings still point to the intended destination and that no older value is overriding the new one.
9. Observe the result long enough to catch delayed processing, caching, queued work, or an intermittent failure.
10. Update internal documentation with the final value, date, owner, result, and any scheduled follow-up.

Verification checklist

• The user is assigned to the intended database
• The application connects and can read and write
• Expected tables and row counts exist
• Non-ASCII text displays correctly
• Unused or overly broad users are removed
• The selected account item, identifier, domain, invoice, user, or service matches the original request.
• The portal no longer shows a pending or failed action unless delayed processing is expected and documented.
• An independent customer-side test produces the expected result.
• Related billing, security, notification, routing, and renewal settings remain correct.
• The previous value and rollback information are retained until the change is proven stable.

Common failure patterns

Use the symptom to narrow the investigation. Do not apply every possible fix at once.

• A prefixed name is shortened incorrectly
• A user is created but not assigned
• The host or port is wrong
• A browser import times out on a large dump
• A restore targets the wrong database
• The correct value was saved on the wrong item, environment, domain, mailbox, record, user, or billing account.
• A dependent setting, external provider, cache, client, or application continues to use an older value.
• The item is pending, suspended, expired, unpaid, cancelled, locked, or otherwise not eligible for the requested action.
• The change completed, but verification reused an authenticated session or cached result that hid the actual behavior.
• A temporary error was treated as permanent and followed by multiple conflicting edits.

Security, privacy, and data handling

• Use a unique password stored in a reputable password manager and enable two-factor authentication for every account user who can access it.
• Give each person an individual account user instead of sharing the owner login. Remove access promptly when responsibilities change.
• Do not send passwords, two-factor recovery codes, full payment-card data, private keys, API secrets, or unredacted identity documents in a normal support reply.
• Review unexpected sign-in notices, permission changes, domain changes, payment changes, and credential resets as possible security events.
• After an access-related incident, rotate affected credentials, review delegated users and contacts, verify domains and DNS, and document the recovery actions.
• Limit access to databases and database users to people who need it and review that access when responsibilities change.
• Before sharing evidence involving full names, hosts, ports, credentials, assignments, privileges, application configuration, and credential rotation, redact information that is not required to diagnose the issue.

When to contact Spark Rack

Contact Spark Rack when the account shows a failed or inconsistent provider-side action, the required control is missing despite confirmed eligibility and permission, data restoration or protected logs are required, an unauthorized change is suspected, or the problem remains after a controlled rollback and independent verification.

• The account email address and the exact service, domain, invoice, ticket, or other item involved
• The page and section used, including the tab or subtab, without copying session tokens from the address bar
• The expected result and the actual result in separate sentences
• The approximate time of the last successful use and the first failure, including the time zone
• The exact error text, response code, bounce text, or visible status
• The changes made immediately before the issue, including old and new values when known
• The devices, browsers, networks, applications, or external tools used to reproduce the issue
• The troubleshooting steps already completed and the result of each step

Closeout and ongoing care

After Databases & Users is working, record the final state and remove any temporary access, files, forwarding paths, test records, or broad permissions that were created for the work. Review related expiration dates, renewal settings, payment status, contacts, and alerts so a future administrative event does not recreate the problem.

Keep the support history, change record, and safe verification evidence for as long as they are operationally useful. Periodic review is especially important after staff changes, migrations, major application updates, domain renewals, payment-method changes, or security incidents.