---
title: "Protect code and access keys"
description: "Protect code and access keys, family Build, NIS2 Art. 21(2)(i)"
url: https://www.alt-f1.be/en/table/sc/
organization: ALT-F1 SRL, Brussels (VAT BE 0830.560.718)
---

# Protect code and access keys

Short label: CODE

Family: Build · NIS2 Art. 21(2)(i)
<a id="meaning"></a>

## Meaning

Control where project code is kept, who can change it and how passwords or access keys are detected.

<a id="why"></a>

## Why it matters

A copied project can expose both intellectual property and credentials that enable access to another service.

<a id="actions"></a>

## What you can do

Use company repositories, review access and run credential checks. If a key is exposed, revoke it and investigate its use.

## Services that can help

Sovereign Code provides agreed hosting, access rules and scanning steps. Its project inventory helps identify who owns the code and where it belongs.

- [Sovereign Code](https://www.alt-f1.be/en/sovereign-code.md)

## Official reference — NIS2 Art. 21(2)(i)

> 2. The measures referred to in paragraph 1 shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include at least the following:
>
> — Directive (EU) 2022/2555 (NIS2), Art. 21(2)

> (i) human resources security, access control policies and asset management;
>
> — Directive (EU) 2022/2555 (NIS2), Art. 21(2)(i)

**What this reference concerns:** People and access: who may access what, how accounts are given and taken away, and an inventory of what you own.

[Read the article on EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555#art_21) · Official text, quoted from the Official Journal of the EU