# CONTENTUM documentation

> What CONTENTUM does and how to use every part of it: project market, tenders, security check, vulnerability database, security tools, team workspace and agent access. With use cases and user stories.

Updated: 2026-11-10 · https://contentum.com/docs/

## Summary

CONTENTUM.COM is a project market for cybersecurity and IT infrastructure. It shows where security work is needed and who can do it, and it gives both sides a short way to each other.

The public site lists open projects and public tenders, describes twelve service areas and offers tools: a passive security check for a domain, a NIS2 self-check, a vulnerability database and guides for buyers. The site is available in 20 languages.

Behind a login, the team runs the security tools (domain map, host check, Deep Scan with a report of about 40 pages, findings board) and the workspace for projects, providers and requests.

AI agents reach the public functions through an MCP server, an A2A agent, WebMCP and a JSON API, without an API key.

- Find open security and infrastructure projects by service, country and region
- Find public tenders with an open deadline
- Check a domain from outside and get a report
- Test whether NIS2 probably applies to an organisation
- Look up any CVE and the vulnerabilities that are being exploited
- Send a request and get matching providers
- Map a domain, run a Deep Scan and track the findings on a board (team)
- Let an AI agent do all public steps on its own

## 1. What CONTENTUM is

The parts of the system and who each part is for.

URL: https://contentum.com/docs/overview/

### The problem it solves

A company that needs a security operations centre, an incident response team or a network rebuild rarely knows which provider fits. A provider rarely knows which company needs it right now. Both search by hand.

CONTENTUM reads public signals of demand, sorts them by service and place, and brings the two sides together on request.

### Three areas

- Public site: projects, tenders, countries, services, tools, guides and this documentation. Open to everyone and to search engines.
- Team area: security tools and workspace. Behind a login.
- Agent access: the public functions as tools for AI agents.

### Who uses it

- Companies and public bodies that need security or infrastructure work
- Service providers: managed security providers, SOC operators, incident responders, network and data centre specialists
- The CONTENTUM team, which answers requests and runs scans
- AI agents that act for one of the three

### What needs no account

Reading projects, tenders, guides and the vulnerability database needs no account. The same is true for the CONTENTUM Check, the NIS2 check and for sending a request.

### Use cases

**First visit as a company**

1. Open the home page and look at the globe.
2. Choose the service area that matches your problem.
3. Read a comparable project to see how others describe the need.
4. Send a request with a short description of the work.

**First visit as a provider**

1. Open Projects.
2. Look at the country and the service you work in.
3. Open a project that fits.
4. Register your interest from the project page.

### User stories

- As an IT manager, I want to see within a minute whether this site covers my problem, so that I do not lose time.
- As the sales lead of a provider, I want to see real demand, so that I know where to offer.
- As an AI agent, I want one description of all functions, so that I can choose the right tool.

## 2. Project market

Open projects on a globe and in a list, each with service, place and signal.

URL: https://contentum.com/docs/projects/

### Where projects come from

Company projects are detected from public job postings. A posting for a security or infrastructure role shows that work is waiting. Public tenders come from official procurement portals.

Sources include the German Federal Employment Agency, the European job portal EURES and tender portals such as TED.

### Signal types

Each project carries the kind of signal it was detected from:

- Security role: the job title names a security function
- Security in job posting: an IT role whose text names security tasks
- Infrastructure role: network, server, cloud or data centre work
- IT role: a general IT position
- Tender: a public tender with an open deadline

### The globe

The home page and the Projects page show a globe. Columns mark countries and projects. The height of a column stands for the score, the colour for the main service. A click on a country opens its ranking and its projects.

### Project list and project page

The list shows each project with service, place and signal. A project page adds the services needed, country and region, the regulations and technologies mentioned, and the date since which the project is known.

### Anonymity

Projects are anonymous. The company name and the source are shared only with matching providers.

### Use cases

**Find demand for a service in a country**

1. Open Projects.
2. Choose the country on the globe.
3. Read the ranking of the country.
4. Open a project.
5. Register your interest.

**Judge a project before you answer**

1. Open the project page.
2. Read the services, regulations and technologies.
3. Check since when the project has been open.
4. Decide whether it fits your team.

### User stories

- As a provider, I want to filter projects by my service and my country, so that I only see work I can do.
- As a market analyst, I want counts per service and country, so that I can size the demand.
- As a company, I want my open need to stay anonymous, so that competitors and attackers learn nothing from it.

## 3. Public tenders

Open public tenders for security and infrastructure work, from the German-speaking countries and from the rest of the world.

URL: https://contentum.com/docs/tenders/

### What is listed

Tenders with an open submission deadline, taken from procurement portals in Europe and other regions. Planned notices without a deadline are left out.

### What a tender page shows

Country, region, type, the deadline as reported, the date of publication and the services needed. The buyer and the original notice are shared with matching providers.

### Deadlines

The deadline is shown as the source reported it. Changes, conditions of participation and the exact cut-off are in the original notice and must be checked there.

### Use cases

**Find tenders you can still answer**

1. Open Tenders.
2. Look at the country or region you serve.
3. Open a tender and note the deadline.
4. Register your interest to receive the original notice.

**Watch a market without visiting many portals**

1. Open Tenders once a week.
2. Compare the list with the week before.
3. Open the new entries for your service.

### User stories

- As a bid manager, I want to see the deadline first, so that I only work on tenders I can still answer.
- As a small provider, I want international tenders in one list, so that I do not have to watch many portals.
- As a public buyer, I want providers to find my tender, so that I receive more offers.

## 4. Countries, regions and services

The same projects, arranged by place and by service area.

URL: https://contentum.com/docs/countries-services/

### Countries

Each country with open projects has its own page with the number of projects and tenders and the demand per service.

### Regions

For Germany there is one page per federal state.

### Twelve service areas

Managed SOC, managed EDR, managed NDR, incident response, first response, vulnerability management, cloud security, ransomware resilience, IT security, network and SD-WAN, digital infrastructure and infrastructure consolidation.

A service page explains what the service covers, the typical tasks, the signal of demand and the number of open projects, and it links to guides on the topic.

### Providers

Providers are checked against their own websites and against official registers before they are listed. The public site shows how many providers cover a service, not their names. Names are shared after a request.

### Use cases

**Compare demand between two countries**

1. Open Countries.
2. Open the first country and note the demand per service.
3. Do the same for the second country.
4. Compare the two.

**Understand a service before you buy it**

1. Open Services.
2. Open the service area.
3. Read the typical tasks.
4. Open a guide on the topic.

### User stories

- As a buyer, I want a plain description of each service, so that I ask providers for the right thing.
- As a provider, I want to see which countries need my service most, so that I can plan where to expand.
- As a journalist, I want figures per country, so that I can quote them with a source.

## 5. Requests: how the two sides meet

One form for companies and providers, a reference number and an answer by e-mail.

URL: https://contentum.com/docs/requests/

### For companies

The contact form asks for company, name, e-mail and a description of the work, plus the services needed. After sending you get a reference number. The team reads the request and answers by e-mail with matching providers.

### For providers

Providers use the same form in the role of service provider. On a project page the button for providers carries the project number into the form.

### Protection against misuse

The form has a captcha, a hidden trap field for bots and a limit on the number of requests per address.

### What happens inside

Each request lands in the request list of the team. From there it can be turned into a project in the workspace.

### Use cases

**Ask for a SOC provider**

1. Open Contact.
2. Describe the systems, the size and the timing.
3. Tick the service areas.
4. Send the form and keep the reference number.
5. Answer the e-mail from the team.

**Answer a project as a provider**

1. Open the project.
2. Press the button for providers.
3. Add your company and your services.
4. Send the form.

### User stories

- As a company, I want to describe my need once, so that I do not have to brief ten providers.
- As a provider, I want to answer one specific project, so that my offer is on point.
- As a team member, I want every request in one list, so that nothing is lost.

## 6. CONTENTUM Check and NIS2 check

Two self-checks: one for a domain, one for the question whether NIS2 applies.

URL: https://contentum.com/docs/check/

### CONTENTUM Check

Enter a domain and confirm that you are authorised to check it. The check looks from outside at the certificate and the TLS versions, the redirect to HTTPS, the security headers, SPF and DMARC for e-mail, security.txt and CAA. It sends only ordinary requests.

The result is a score from 0 to 100, a grade and a report page with one line per check: passed, warning or failed.

### Limits of the check

The check is passive. A good score does not prove that the systems are secure. It shows that the visible basics are in place.

A domain is not checked again within 30 minutes. The earlier result is shown instead.

### NIS2 check

Choose sector and size. The check says whether the organisation is probably covered by NIS2 as an essential or an important entity. Twelve questions on the measures of Article 21 show which ones are open, each with the matching service.

The result is a first orientation, not legal advice.

### Use cases

**Check your own domain before an audit**

1. Open the CONTENTUM Check.
2. Enter the domain and confirm your authorisation.
3. Read the failed and warning lines.
4. Fix them or send a request for help.
5. Run the check again later.

**Find out whether NIS2 applies**

1. Open the NIS2 check.
2. Choose your sector and size.
3. Answer the twelve questions.
4. Read which measures are open.

### User stories

- As an IT manager, I want a quick outside view of my domain, so that I can fix the obvious gaps first.
- As a managing director, I want to know whether NIS2 covers my company, so that I can plan budget and responsibility.
- As a provider, I want to show a prospect their score, so that the first talk starts with facts.

## 7. Vulnerability database

Every published CVE, and the ones that are being exploited right now.

URL: https://contentum.com/docs/vulnerabilities/

### What is in it

More than 400,000 published CVE records, arranged by year and by vendor, with description, CVSS score, weakness type and references.

A separate list holds the vulnerabilities known to be actively exploited, taken from the CISA KEV catalog, with the required action and the due date.

### How to find a record

Search by CVE number, or browse by year or by vendor. Each record has its own page.

### From a vulnerability to help

Each record names the service areas that deal with this kind of weakness.

### Sources and freshness

The data comes from the CVE list, the NVD and CISA and is refreshed every day. The pages of the database are in English.

This product uses data from the NVD API but is not endorsed or certified by the NVD.

### Use cases

**Check whether a CVE from a scanner report is being exploited**

1. Open the vulnerability database.
2. Enter the CVE number.
3. Read whether the record is marked as actively exploited.
4. Read the required action and the due date.

**List the vulnerabilities of a vendor**

1. Open the list of vendors.
2. Choose the vendor.
3. Read the newest records first.

### User stories

- As an administrator, I want to know which CVE to patch first, so that I close the dangerous gaps before the others.
- As a security analyst, I want every CVE on a stable address, so that I can link to it in reports.
- As an AI agent, I want CVE facts as structured data, so that I can answer without guessing.

## 8. Guides

Neutral background for buyers, checked against sources.

URL: https://contentum.com/docs/guides/

### Topics

NIS2, penetration testing, DAST and SAST, vulnerability scanning, bug bounty platforms, NIST CSF 2.0, CIS Benchmarks, OWASP Top 10, vulnerability management under ISO 27001, API security and the market in the German-speaking countries.

### How a guide is built

Each guide has sections, questions with answers and a list of the sources it was checked against. It ends with the next step to a provider.

### Languages

A guide appears in a language only when its text exists in that language. There is no machine-made filler.

### Use cases

**Prepare a buying decision**

1. Open Insights.
2. Read the guide on the topic.
3. Note the questions you should ask providers.
4. Send a request.

**Brief a manager in ten minutes**

1. Open the guide.
2. Read the lead and the questions.
3. Pass on the link with the sources.

### User stories

- As a buyer, I want neutral background, so that I can judge the offers I receive.
- As a manager, I want the short version with sources, so that I can decide without reading standards.
- As a provider, I want to send a customer a neutral explanation, so that I do not have to write it myself.

## 9. Security tools: map, Deep Scan, report, board

The tools of the team for looking at a company from outside. Behind a login.

URL: https://contentum.com/docs/security-tools/

### Domain map

Enter a domain. The map finds subdomains from public sources and DNS, resolves their addresses and networks, and makes one ordinary web request per host. The drawing connects host, address and network. The table lists each host with its systems and observations.

A map usually takes less than two minutes.

### Host check

From the map, a single host can be checked in more depth. This needs the confirmation that the owner agrees. The result is a short report in English or German, as HTML or PDF.

### Deep Scan

A Deep Scan analyses up to ten web hosts of the domain: headers, redirects, cookies and page source; TLS and certificates; DNS and mail records; a port scan of common service ports; known vulnerabilities and misconfigurations. It runs for 15 to 30 minutes.

The scan is non-intrusive: no exploitation, no password guessing, no fuzzing and no load tests.

### Permission

Active checks start only after the user confirms that the owner has given permission. The confirmation is logged and printed in the report.

### The report

About 40 pages: summary with score and grade, findings by severity with evidence and fix, TLS, headers, network, DNS and e-mail, technology, the mapping to NIS2 Article 21, ISO 27001 Annex A and GDPR Article 32, a plan in phases and the method.

The report is available as HTML and as PDF on light or dark paper. It is written in English.

### Findings board

Every scanned domain is a project with its own board. The findings are cards in five columns: Open, In progress, Fixed to verify, Verified and Accepted risk. A card is moved by drag and drop or inside the card. Every change is stored with time, person and note.

A new Deep Scan updates the board by itself: new findings appear in Open, findings that are gone move to Verified, and findings that return after a fix go back to Open.

### Use cases

**Look at a prospect before the first call**

1. Open Tools.
2. Enter the domain and start the map.
3. Read the hosts, networks and observations.
4. Use the facts in the call.

**Run a Deep Scan for a customer**

1. Get the permission of the owner.
2. Create the map of the domain.
3. Start the Deep Scan and confirm the permission.
4. Wait 15 to 30 minutes.
5. Open the report and send the PDF.

**Track the fixing of findings**

1. Open the board of the project.
2. Move each card as the work proceeds.
3. Run a new Deep Scan after the fixes.
4. Check which cards the scan moved to Verified.

### User stories

- As a consultant, I want a map of a domain in two minutes, so that I am prepared for the first call.
- As a customer, I want a report with evidence and a fix for each finding, so that my team knows what to do.
- As a project lead, I want to see the status of every finding, so that I can report progress.
- As an auditor, I want to see when a status changed and who changed it, so that the process can be traced.

## 10. Team workspace

Where the team works on projects, providers and requests. Behind a login.

URL: https://contentum.com/docs/workspace/

### Overview and project list

The overview shows what is new and what is waiting. The list holds all projects with signal, score and stage and can be exported as CSV.

### Project record

Each project has a stage, an owner, a next step with a date, a contact, notes and a log of changes.

### Board and map

The board shows the projects by stage. The map shows them by place.

### Matrix and providers

The matrix sets the open projects against the listed providers. The provider list holds each provider with services, the way it was verified, stage and notes, and can be exported as CSV.

### Signals, requests and data

Signals shows the results of the passive check for projects with a known website and the latest runs of the public CONTENTUM Check. Requests holds what came in through the form and from agents. Data shows the state of the data and offers import and export as CSV.

### Use cases

**Turn a request into a project**

1. Open Requests.
2. Read the new request.
3. Create a project from it.
4. Set the owner and the next step.

**Prepare the week**

1. Open the overview.
2. Open the board and look at each stage.
3. Set the next step with a date for every project that is waiting.

### User stories

- As a team member, I want one place for projects, providers and requests, so that I do not need a second tool.
- As a team lead, I want to see the stage and the owner of each project, so that nothing stands still unnoticed.
- As an analyst, I want to export the lists, so that I can evaluate them elsewhere.

## 11. Agent access

The public functions as tools for AI agents. No API key.

URL: https://contentum.com/docs/agents/

### Four ways in

- MCP server at /mcp (Streamable HTTP)
- A2A agent at /a2a with an agent card at /.well-known/agent-card.json
- WebMCP on the page /agents/ for agents inside the browser
- JSON API under /agents/api, described by /agents/openapi.json

### What agents can do

Search projects and tenders, read service areas, countries and provider coverage, look up vulnerabilities, read guides, run the CONTENTUM Check, test the NIS2 scope, send a request for a company or a provider and ask for its status.

- `search_projects`: Open cybersecurity and IT infrastructure projects and public tenders by service, country and words.
- `get_project`: One project or tender by id (CT-0001): services, country, signal, regulations, technologies, deadline.
- `list_services`: The 12 service areas with their open project counts.
- `get_service`: One service area: description, typical tasks, demand signal, open projects, provider count.
- `list_countries`: Countries with counts of company projects, tenders and listed providers.
- `get_country`: One country: open projects by service, tenders, providers by service, latest projects.
- `get_provider_coverage`: How many listed providers offer a service in a country (counts only).
- `get_market_stats`: Totals: open projects, tenders, countries, demand per service and regulation, data date.
- `search_vulnerabilities`: CVE records by vendor or year, or the actively exploited ones (CISA KEV).
- `get_vulnerability`: One CVE: description, CVSS, weaknesses, references and whether it is actively exploited.
- `list_guides`: Buyer guides (NIS2, penetration testing, ISO 27001, OWASP …) in a given language.
- `get_guide`: Full text of one guide with sections, questions and sources.
- `run_domain_check` (sends data): Passive security check of a domain: TLS, security headers, SPF, DMARC, security.txt. Returns score and report link.
- `check_nis2_scope`: Whether an organisation is probably covered by NIS2, from sector and size.
- `get_platform_info`: What CONTENTUM does, what a request needs, contacts, languages and the agent endpoints.
- `submit_project_request` (sends data): A company describes the work it needs. Returns a request id; the team replies by e-mail.
- `register_provider_interest` (sends data): A service provider asks to be listed or registers interest in a project. Returns an id.
- `get_request_status`: Status of a request (id + e-mail).

### Limits and privacy

Reading tools are open, with a limit per address. Tools that send data have a tighter limit. Agents see what the public pages show: no company names, and providers as counts only.

The domain map and the Deep Scan are not open to anonymous agents, because they need the permission of the owner.

### Machine-readable descriptions

llms.txt and /agents/llms.txt describe the site and the tools for language models. The OpenAPI file, the agent card and the MCP server card describe the interfaces. This documentation is available as one Markdown file per language at /docs/docs.md.

### Use cases

**An agent finds a provider for its principal**

1. Call search_projects or get_provider_coverage to see the market.
2. Call submit_project_request with company, e-mail and description.
3. Keep the request number.
4. Call get_request_status later and report back.

**An agent answers a security question**

1. Call get_vulnerability for the CVE in question.
2. Call list_guides and get_guide for the background.
3. Call run_domain_check for a domain the principal is authorised to check.
4. Give the answer with the links from the results.

### User stories

- As an AI agent, I want to send a request without a form or captcha, so that I can finish the task for my principal.
- As a developer, I want an MCP endpoint without registration, so that I can connect my assistant in a minute.
- As the operator, I want agents to see only public data, so that no company name leaks.

## 12. Data, privacy and languages

Where the data comes from, what stays private, and the 20 languages.

URL: https://contentum.com/docs/data-languages/

### 20 languages

English is the main language and German has its own pages. The other languages are Spanish, French, Portuguese, Italian, Dutch, Polish, Turkish, Russian, Ukrainian, Arabic, Persian, Urdu, Hindi, Chinese, Japanese, Korean, Vietnamese and Indonesian. Arabic, Persian and Urdu are set from right to left.

Titles of tenders, place names and the vulnerability database stay in their original language.

### Freshness

The date of the project data is given in llms.txt and by the agent tool get_market_stats. The vulnerability database is refreshed every day.

### Privacy

Names of companies and buyers are not published. Requests are stored in order to answer them. A check stores the domain and its result. Details are in the privacy notice.

### For search engines and AI

There is one sitemap per language with all language versions of each page, structured data on every page, and the files llms.txt and llms-full.txt. The public pages are open to search engines and AI crawlers. The team area is closed to them.

### Known limits

- Demand is inferred from public signals. A position can be filled or withdrawn before the data is refreshed.
- Checks and scans look from outside only.
- The Deep Scan report is in English.
- Statements on legal topics such as NIS2 are orientation, not legal advice.

### Use cases

**Quote CONTENTUM figures**

1. Open llms.txt or call get_market_stats.
2. Take the figure together with the date of the data.
3. Name CONTENTUM.COM as the source.

**Read the site in your language**

1. Open the language menu at the top.
2. Choose your language.
3. The address of each page changes to your language code.

### User stories

- As a reader, I want the site in my language, so that I understand the details.
- As a data protection officer, I want to know what is stored, so that I can assess the use of the site.
- As a search engine or AI crawler, I want clean language versions and structured data, so that I index the right page for each language.
