When a DACH company brings in a remote engineering team, the security conversation often starts in the wrong place: with certificates. Certificates matter, but they describe a provider's management system, not the specific controls that protect your repositories, secrets and data in this engagement. A better starting point is a short, enforceable baseline covering identity, devices, secrets, data, logging and incident reporting, agreed before the first access is granted and mapped to the frameworks your auditors and customers already use. This guide sets out such a baseline and explains how it relates to ISO/IEC 27001, TISAX and the DSGVO.

The numbers: the threat picture in 2025 and 2026

Security requirements for remote teams are rising because the threat level is. Bitkom's 2025 economic protection study put the damage to German companies from theft, espionage and sabotage at a record 289.2 billion EUR, with 87% of companies affected and around 70% of the damage caused by cyberattacks. The BSI counted an average of 119 newly discovered vulnerabilities per day in its 2025 situation report. Breaches stay hidden for long periods: IBM's Cost of a Data Breach Report 2025 measured an average of 241 days to identify and contain a breach. Regulation is widening the circle of obligations. Germany's NIS2 implementation law took effect on 6 December 2025 and extends supervision to roughly 29,500 entities, up from about 4,500. In automotive, ENX reported that more than 20,000 locations worldwide held a valid TISAX label in December 2025, with India among the five countries with the most assessed sites. Certificates are widespread; what differs is the control set behind them.

Frameworks: what they do and do not tell you

ISO/IEC 27001 specifies requirements for an information security management system. The 2022 edition contains 93 reference controls in Annex A, grouped into organisational, people, physical and technological themes. A certification shows that an organisation runs such a management system within a defined scope. It does not show that every control applies to your engagement, so always check the certificate's scope and the statement of applicability.

TISAX is the assessment and exchange mechanism used in the automotive industry, operated by the ENX Association and based on the VDA Information Security Assessment catalogue. Results are shared as labels through the ENX platform, at assessment levels that differ in depth, with the higher levels involving more thorough verification. If your customers are automotive OEMs or tier suppliers, they may require a TISAX label from you and expect equivalent controls from your subcontractors, especially where prototype data is involved.

DSGVO applies wherever the remote team may process personal data. A processor relationship requires a contract under Art. 28 DSGVO. India has no adequacy decision under Art. 45 DSGVO, so transfers usually rely on the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) under Art. 46, accompanied by a transfer impact assessment and supplementary measures where needed.

The baseline below does not replace these frameworks. It is the subset of controls that should be in place from day one of a remote engagement, whatever the certification status.

The baseline, control by control

1. Identity and access

  • Named, individual accounts in the client's identity provider. No shared accounts, no shared credentials.
  • Multi-factor authentication on every system, preferably phishing-resistant methods such as hardware keys or platform authenticators.
  • Least privilege by role: delivery engineers receive what the sprint requires, production access is separate and time-bound.
  • A documented joiner and leaver process with a defined maximum time from departure to revocation, and a monthly access review.

2. Devices

  • Company-managed devices only, enrolled in device management, with full-disk encryption, automatic screen lock, current patches and endpoint protection.
  • No client source code or data on personal devices.
  • Defined rules for removable media and local copies of repositories.

3. Secrets

  • All secrets in a central secrets manager owned by the client, never in code, chat or tickets.
  • Secret scanning in CI and as a pre-commit hook.
  • Rotation of all secrets an engineer had access to when that engineer leaves the engagement.

4. Data

  • No production personal data in development or test environments. Use synthetic or properly anonymised data.
  • Where production access is unavoidable, it is restricted, logged and covered by the Art. 28 contract and the transfer mechanism.
  • Data classification agreed at kickoff, so that engineers know what may leave which system.

5. Network and environments

  • Access to internal systems through the client's VPN or a zero-trust access layer, not through exposed services.
  • Separation of development, staging and production, with different credentials.

6. Logging and monitoring

  • Audit logs for access to repositories, CI, cloud consoles and production, retained according to the client's policy.
  • Alerts for unusual access patterns, such as mass repository cloning or access from unexpected locations.

7. Incident reporting

  • A written obligation for the provider to report suspected security incidents to a named client contact without undue delay, consistent with Art. 33 Abs. 2 DSGVO for processors.
  • A tested contact chain on both sides, including outside working hours.

Mapping the baseline

Baseline areaISO/IEC 27001:2022 Annex A themeTypical evidence
Identity and accessOrganisational and technological controls on access and authenticationIdP configuration, access review records
DevicesTechnological controls on user endpoint devicesDevice management report
SecretsTechnological controls on authentication information and cryptographySecrets manager audit log, scanning results
DataOrganisational controls on classification and transfer, technological controls on maskingData classification, test data concept
LoggingTechnological controls on logging and monitoringLog retention configuration
IncidentsOrganisational controls on incident managementIncident procedure, contact list
PeoplePeople controls on screening, awareness and confidentialityTraining records, confidentiality undertakings

Questions to ask any remote provider

  1. Which certifications do you hold, what exactly is in scope, and can we see the statement of applicability?
  2. Are all engineers on managed devices with encryption and endpoint protection, and how do you evidence this?
  3. Will you work exclusively in our accounts and identity provider?
  4. What is your process and maximum time for revoking access when an engineer leaves?
  5. How do you handle personal data, and which transfer mechanism do you propose?
  6. Who is your incident contact, and how quickly will we hear from you?
  7. Will you accept our security policy as an annex to the contract and allow evidence requests?

Proportionality

Not every engagement needs every control at maximum strength. A team building an internal analytics tool on synthetic data has a different risk profile from a team with access to vehicle prototype data or medical device software. Agree the baseline first, then decide consciously where to go further. Whatever provider you choose, the decisive step is to write the baseline into the contract and verify it with evidence, rather than accepting a certificate logo as a substitute.

This article is general information and does not constitute legal advice.

A baseline written into the contract and verified with evidence protects you more than any logo on a slide. Our security and compliance overview sets out how niogod™ applies these controls in its pods, so that you can test them against your own requirements. If a remote team with access to sensitive code or data is on your roadmap, it is a conversation worth having before the first credential is issued.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights