Guide

Born in the Cloud: Fundamental Security Layers for the Modern Startup

For a startup, the office is often just a set of SaaS subscriptions. Working cloud-native is fast, but it also creates entry points that are complex and hard to see. These are the cloud security layers a startup should put in place early, while the setup is still small.

By SecureBusinessHub Editorial, International cybersecurity desk · · 8 min read

1. The shared responsibility model

The most common startup mistake is assuming that AWS, Azure, or Google Cloud handles security automatically. They handle security of the cloud: the physical data centres and underlying hardware. You're responsible for security in the cloud: your data, your configurations, and your access controls.

If you leave an S3 bucket publicly accessible, that's not AWS's failure. It's yours.

Data residency and sovereignty

In 2026, where your data physically lives matters legally. For businesses with international clients, you need to know which region your cloud data is stored in to stay compliant with GDPR or the CCPA. Mismanaging this creates legal exposure even when the technical security is solid.

2. Identity: the new perimeter

In a cloud environment, identity is what separates your data from everyone else's, so IAM comes first.

  • MFA on every account: No exceptions, regardless of how minor the role seems.
  • No root accounts for daily tasks: Lock the admin or root account away. Use granular roles for regular work.
  • Just-in-time access: Don't give developer accounts permanent access to production. Use tools that grant temporary access only when it's needed.

3. Shadow IT in the startup context

Startups often run on dozens of secondary tools: Slack, Trello, Notion, GitHub. Each one is a potential entry point. Use Single Sign-On to consolidate logins. When someone leaves, one account deactivation removes their access to everything, rather than hunting through fifty separate admin panels.

4. Infrastructure as code

Managing cloud configuration through a web console is an invitation to human error. Use code to manage infrastructure: Terraform, Pulumi, and similar tools let you peer-review every change for security issues before anything gets deployed.

5. Cloud Security Posture Management (CSPM)

Cloud configurations change constantly, and new vulnerabilities surface regularly. CSPM tools run automated scans that alert you when a firewall rule changes or an unencrypted database becomes internet-accessible.

Setting up a CSPM tool early means your security awareness scales with your infrastructure. You stop guessing about your security status and start checking it continuously.

NIS2 requirements: the second regime to know about

Data protection law is not the only European regime a business gets asked about. The NIS2 directive sets baseline cybersecurity and incident-reporting obligations for organisations in a defined list of sectors, and it is the source of most of the security questions that now arrive attached to contracts. The two regimes cover different ground: data protection law governs personal data and what people can ask you to do with it, while the NIS2 requirements govern the security and resilience of network and information systems, whether or not personal data is involved. A single incident can engage both, on separate clocks, to separate authorities.

The directive applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet above ten million euros. Under that size rule, a ten-person company is usually not regulated by the directive at all. The requirements can still reach you, because one of them is supply chain security: organisations inside scope are expected to consider the security practices of their direct suppliers, and in practice that expectation arrives as a questionnaire in your inbox.

The measures the directive names are a reasonable checklist for any business, which is why they are worth knowing even when they do not apply to you directly. They cover risk analysis and written security policies, incident handling, business continuity and backups, supply chain security, secure development and vulnerability handling, basic cyber hygiene and training including for management, encryption and access control policies, and multi-factor authentication. Reporting is staged and fast for the organisations it covers: an early warning within twenty-four hours of becoming aware of a significant incident, a fuller notification within seventy-two hours, and a final report within one month.

Because the directive is national law in each member state rather than a single rulebook, the details of scope, thresholds and reporting differ by country. For a fuller explanation of the instrument itself, see our guide to what the NIS2 directive is, and for the supplier side of the supply chain obligation, our walkthrough of vendor risk assessment. The reporting clocks that run alongside data protection deadlines are covered in data breach notification requirements.

Frequently asked questions

Does NIS2 apply to a small business?

NIS2 generally applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet total above ten million euros. A smaller business falls outside its direct scope unless a member state has specifically designated it or it sits in one of the size-independent categories, such as DNS service providers or trust service providers. Being outside scope does not stop the directive reaching you through customers who are inside it.

What is the difference between GDPR and NIS2?

GDPR governs personal data: what you may collect, why you may hold it, and what rights people have over it. NIS2 governs the security and resilience of network and information systems in specific sectors, whether or not personal data is involved. One incident can engage both regimes at once, on separate reporting clocks and to separate authorities.

How long do you have to report a data breach?

Under the European model, a personal data breach is reported to the supervisory authority without undue delay and, where feasible, within seventy-two hours of becoming aware of it, and affected individuals are told without undue delay where the risk to them is high. Organisations in scope of NIS2 carry a separate obligation: an early warning within twenty-four hours, a fuller notification within seventy-two hours, and a final report within one month.

Does a small business need a data protection officer?

Under GDPR a data protection officer is required where the organisation is a public authority, where its core activities involve regular and systematic monitoring of people on a large scale, or where its core activities involve large-scale processing of special category or criminal offence data. A small business that meets none of those tests is not required to appoint one, though naming someone internally as the contact for privacy questions is worth doing regardless.

What should a small business do when a client's security questionnaire asks about NIS2?

Answer with what you do now rather than what you think the client wants to hear. The questions usually cover written security policies, incident handling and how fast you would notify them, multi-factor authentication, access control when staff join and leave, backup and recovery arrangements, and which of your own subprocessors touch their data. Gaps are common, and disclosing one with a date for closing it lands far better than an answer that does not survive the follow-up question.

Do these rules reach a business based outside the EU?

They can. GDPR reaches organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour, and other regions have their own regimes with their own triggers. NIS2 obligations follow the sectors and the member states that transpose it, but its supply chain expectations travel through contracts, which is how they reach suppliers anywhere in the world.

Related reading