In short
- Sign-in: company sign-in (SSO) or strong passwords with a second factor (MFA), lockout after failed attempts, sign-out after inactivity.
- Permissions: everyone sees and does only what they need; enforced on the server, not just hidden in the interface.
- Encrypted connections (HTTPS) always, and sensitive data in the database too; passwords stored only as hashes.
- Regular library and server updates, backups following the 3-2-1 rule with a restore test.
- Logs of who changed what and when, a security test before launch (e.g. against the OWASP Top 10) and a data processing agreement if the vendor has access to personal data.
The minimum list
| Area | Minimum | How to check at acceptance |
|---|---|---|
| Sign-in | SSO or passwords with MFA, lockout after failed attempts, sign-out after inactivity | Try signing in without the second factor, and several times with a wrong password |
| Permissions | Roles, least privilege, checks on the server | Sign in as a regular user and try to open someone else's record by URL |
| Encryption | HTTPS everywhere, sensitive data encrypted, passwords as hashes | Check the certificate, ask how passwords are stored |
| Updates | A list of dependencies, regular updates, security patches applied quickly | Ask for a report of dependencies and their versions |
| Backups | 3-2-1 rule, automatic backups, restore test | Ask for the result of the latest restore test |
| Logs | Who changed what and when; sign-ins and errors; no passwords or full data in logs | Change a record and check the history entry |
| Testing | A security test before launch, e.g. against the OWASP Top 10 | Ask for the report and the list of fixes |
Backups: the 3-2-1 rule
Three copies of the data, on two different media or services, one of them in another location. The most important part, though, is the restore test: a backup nobody has restored is only a hope. It is worth agreeing how much data the company can afford to lose (e.g. the last hour) and how quickly the system has to be back after a failure.
GDPR and vendor access
- If the vendor has access to personal data (rollout, maintenance), a data processing agreement is needed.
- Use anonymised data in test environments, not copies of production.
- Vendor access should be personal, with MFA, and revoked when the work ends.
- Change history and logs help show who had access to the data.
What to put in the request and the contract
Security requirements are best written into the request for proposal: then they are in the quote rather than an extra at the end. In the contract it is worth adding: handover of code and access, how vulnerabilities are reported and the response time, responsibility for updates during maintenance, and a data processing agreement.
2Simple designs apps with roles, change history and access control from the first version, runs software testing (including backend and API) and hands over the code, documentation and access at acceptance.