Projectmatch Deutsch

Security clearance for IT contracts in Germany: how often Ü1, Ü2 and Ü3 are required

3.2% of IT freelance listings in Germany require a security clearance (Sicherheitsüberprüfung): 1,422 of 44,301 listings, on average 356 a month. The level asked for most is Ü2, the extended security check – named by 70% of the listings requiring a clearance. Below: which levels are demanded, in which developer roles, month by month, and what a clearance means for contractors.

By . Data: 44,301 project listings from German IT freelance project boards, July 2026 – October 2026. Published , last updated .

What do Ü1, Ü2 and Ü3 mean?

The levels come from the German federal Security Clearance Check Act (Sicherheitsüberprüfungsgesetz, SÜG, in German), which defines three kinds of security check (§ 7 SÜG). The short forms Ü1, Ü2 and Ü3 – also SÜ1, SÜ2 and SÜ3 – are used for instance by the Federal Foreign Office (in German).

Which clearance level do the listings require?

70% of the listings requiring a clearance ask for Ü2, 2.7% for Ü1 and 1.9% for Ü3. 26% require a security clearance without naming the level. Of all listings, 2.2% require Ü2.

  1. Ü1 – basic security check39 listings2.7%
  2. Ü2 – extended security check992 listings70%
  3. Ü3 – extended check with security investigations27 listings1.9%
  4. no level named364 listings26%

Security clearance in development, consulting and operations

Projects without development work – such as consulting, project management, administration, IT operations and non-IT work – make up 54% of the listings requiring a clearance. Of these projects, 2.5% require one; of the development projects, 4.9%.

  1. All listings1,422 of 44,301 listings3.2%
  2. Development projects653 of 13,254 listings4.9%
  3. Projects without development work769 of 31,047 listings2.5%

Security clearance by developer role

The highest share of listings requiring a clearance is in the role DevOps / Platform Engineer (13%), the lowest in PLC / Automation Programmer (0%). Below each role: the listings requiring a clearance, all listings of the role, and how many of them ask for Ü2.

  1. DevOps / Platform Engineer227 of 1,760 listings · Ü2: 16013%
  2. Security Engineer114 of 903 listings · Ü2: 8213%
  3. Cloud Solution Architect22 of 348 listings · Ü2: 116.3%
  4. Test Engineer70 of 1,152 listings · Ü2: 486.1%
  5. Python Developer19 of 321 listings · Ü2: 145.9%
  6. Java Backend Developer42 of 1,001 listings · Ü2: 384.2%
  7. ML / AI Engineer27 of 756 listings · Ü2: 253.6%
  8. React Developer8 of 311 listings · Ü2: 62.6%
  9. Embedded C/C++ Developer16 of 741 listings · Ü2: 102.2%
  10. Data Engineer21 of 1,075 listings · Ü2: 182%
  11. Low-Code Platform Developer14 of 746 listings · Ü2: 101.9%
  12. Java Fullstack Developer12 of 657 listings · Ü2: 101.8%
  13. SAP Developer13 of 912 listings · Ü2: 81.4%
  14. C# / .NET Developer6 of 471 listings · Ü2: 41.3%
  15. PLC / Automation Programmer0 of 601 listings · Ü2: 00%

Security clearance month by month

The table shows per month the share of listings requiring a clearance, their number and the share of Ü2 among them. From September 2026 to October 2026 the share rose by 0.9 percentage points.

Listings requiring a security clearance per month of listing
Monthshare requiring a clearancelistingsof which Ü2Change of the share (percentage points)
July 20263.2%32068%
August 20263.3%33964%+0.1
September 20262.7%29674%−0.6
October 20263.6%46772%+0.9

What a security clearance means for IT contractors

The points below restate what the law and the linked sources say; they are not legal advice. What applies to a particular contract is for the client to clarify.

Can I apply for a security clearance myself?

No. A check is carried out on a person who is to be entrusted with a security-sensitive activity, and only with their written consent (§ 2 SÜG). For contracts from private companies the competent authority is in principle the Federal Ministry for Economic Affairs and Energy; within the company a security officer (Sicherheitsbevollmächtigter) handles the procedure (§ 25 SÜG). The German digital association Bitkom writes in its position paper on practical classified-information protection (July 2026, in German) that the procedure has to be initiated by a contracting authority, so companies cannot qualify in advance.

How long does a security clearance take?

In the same paper Bitkom reports processing times of often several months. Ask early whether and when the client will initiate the check.

Does an earlier clearance carry over to the next contract?

It may. If a check of the same or a higher level was completed less than five years ago without finding a security risk, a new one may be waived (§ 2(1a) SÜG) – the authority may do so, it does not have to.

Time abroad and foreign nationals

The check usually covers the last five years. For anyone who lived abroad for more than six months at a stretch in that time, the security authorities of that country can be queried – only with separate consent, and the query is dropped among other reasons when that country lacks an adequate level of data protection. For foreign nationals other than EU citizens with freedom of movement, the authority can query the Central Register of Foreign Nationals (all § 12 SÜG).

How long is a security clearance valid?

Not indefinitely. After five years the security declaration is usually updated, after ten years a repeat check is usually initiated (§ 17 SÜG).

The projects page lists the current listings; Projectmatch matches new projects against your profile automatically. Try it now.

See also: Most in-demand developer roles in German IT freelance projects, IT contract length in Germany, How remote are IT freelance projects? and English-speaking IT contracts in Germany.

Method

An AI model reads every project description and records a security clearance only when the description explicitly requires one: the level Ü1, Ü2 or Ü3 – spellings such as "SÜ2" or "Ü 2" count as Ü2 – or "no level named" when none is given. It does not distinguish whether a listing requires an existing clearance or only the willingness to undergo one. The shares refer to all analysed listings of a period. Roles and kinds of project are those of the developer-roles analysis; roles with fewer than 300 listings are left out, because a share of a few percent depends too much on chance with fewer listings to compare roles.

Every project has been analysed this way since July 2026; the figures here start in July 2026 and refer to the projects first listed in a month. They are updated monthly and published under CC BY 4.0: you may reuse them freely, also commercially, crediting "Projectmatch (projectmatch.io)" and, online, linking to this page.