2Simple
  • Home
  • Services
    • Custom software
    • Web and mobile apps
    • Process automation and AI
    • Document workflow
    • ERP integrations
    • Team augmentation
    • Software testing
  • Industries
    • Medical distribution
    • Logistics
    • Manufacturing and warehousing
    • Finance and insurance
    • Maritime and ports
    • Facility management
    • Energy and renewables
    • Other industries
  • Portfolio
  • Tools
    • Project brief builder
    • Process cost calculator
    • Software acceptance checklist
  • About
    • Company
    • References
PL EN
Contact us
2Simple
  • Home
  • Services
    • Custom software
    • Web and mobile apps
    • Process automation and AI
    • Document workflow
    • ERP integrations
    • Team augmentation
    • Software testing
  • Industries
    • Medical distribution
    • Logistics
    • Manufacturing and warehousing
    • Finance and insurance
    • Maritime and ports
    • Facility management
    • Energy and renewables
    • Other industries
  • Portfolio
  • Tools
    • Project brief builder
    • Process cost calculator
    • Software acceptance checklist
  • About
    • Company
    • References
Contact us
PL EN

Business app security: the minimum worth requiring

Most incidents in business apps do not come from sophisticated attacks but from missing basics: weak sign-in, overly broad permissions, outdated libraries and backups nobody has checked. Below is a minimum list worth putting in your request for proposal and checking at acceptance.

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

AreaMinimumHow to check at acceptance
Sign-inSSO or passwords with MFA, lockout after failed attempts, sign-out after inactivityTry signing in without the second factor, and several times with a wrong password
PermissionsRoles, least privilege, checks on the serverSign in as a regular user and try to open someone else's record by URL
EncryptionHTTPS everywhere, sensitive data encrypted, passwords as hashesCheck the certificate, ask how passwords are stored
UpdatesA list of dependencies, regular updates, security patches applied quicklyAsk for a report of dependencies and their versions
Backups3-2-1 rule, automatic backups, restore testAsk for the result of the latest restore test
LogsWho changed what and when; sign-ins and errors; no passwords or full data in logsChange a record and check the history entry
TestingA security test before launch, e.g. against the OWASP Top 10Ask 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.

Contents

  1. The minimum list
  2. Backups: the 3-2-1 rule
  3. GDPR and vendor access
  4. What to put in the request and the contract

Software acceptance checklist

Checkpoints for acceptance, including security, backups and handover of access - with a protocol template.

Open the checklist

Frequently asked questions

Does a small business app need a security test?

Yes, at least a basic one, if it processes personal data or is reachable from the internet. A review against the OWASP Top 10 finds the most common mistakes, such as access to someone else's data by changing the URL.

Is MFA necessary?

For apps reachable from the internet that process company data - definitely worth it. The simplest way is company sign-in (e.g. Microsoft or Google), which already has a second factor.

How often should libraries be updated?

Regularly, e.g. once a month as part of maintenance, and patches for critical vulnerabilities as soon as possible after they are published.

Who is responsible for security after launch?

That has to be agreed in the maintenance contract: who updates the server and libraries, who monitors the logs and how quickly a reported vulnerability is handled.

Related

  • Software testing
  • User acceptance testing (UAT)
  • Cloud or on-premise
  • How to write a software RFP
  • All guides

Let's talk about your project

Describe in a few sentences what you want to build or improve: an app, a platform, an integration or a process. We reply within one business day. The first call is an analysis, not a sales pitch.

Write to us or email office@2simple.it
2Simple

A software house from Poland. We design and build web, mobile and desktop applications, platforms, integrations, automations and AI solutions for companies.

Services

  • Custom software
  • Web and mobile apps
  • Process automation and AI
  • Document workflow
  • ERP integrations
  • Team augmentation
  • Software testing

Company

  • About
  • References
  • Portfolio
  • Free tools
  • Guides
  • Contact

Company details

2Simple Sp. z o.o. Henryka Sienkiewicza 13/13A 97-300 Piotrków Trybunalski NIP 7712926973 KRS 0001054625 office@2simple.it LinkedIn
Privacy policyCookies policyTemporary files
PL EN
© 2026 2Simple Sp. z o.o.