ENISA publications
The newest publications on the European Union Agency for Cybersecurity's publications page: title, date, link and the topics ENISA gives, for cyber.promptugal.news. ENISA has no feed, so the HTML list (one page) is read. No report text is kept.
Three layers: the source (who publishes it, the terms, when it was read), the raw data as the publisher served it, and the processed data, what this site makes of it. The processing is where the value is: named fields, places joined, gaps marked, every value kept with its source and time.
1. The source
At a glance
| Field | Value |
|---|---|
| Publisher | ENISA (European Union Agency for Cybersecurity) |
| Source | https://www.enisa.europa.eu/ |
| Reader page | https://www.enisa.europa.eu/publications |
| Schedule | every 6 hours: the Pages workflow (.github/workflows/pages.yml) at 17 minutes past 00, 06, 12 and 18 UTC; one GET of the first page of ENISA's publications list (robots.txt allows /publications to everyone; Crawl-delay 10 respected; a refusal is recorded and respected); every other run keeps the last read, copied from the live site. Moved back from on-hold on 18 Nov 2026. Dinis decided (18 Nov 2026, about 23:40 UTC, in cyber.b@'s session; PrompTugal__News__Cyber board/team/cyber/briefs/2026-11-18-dinis-answers.md, relayed): "I don't think we are a crawler per se ... we're just trying to use data that they have ... I'm assuming that [ENISA] published data available in APIs". So ENISA is read through its published interfaces. Our collector is plain code with its own named user agent, and the path it reads is allowed to *. |
| Owner | data.b@PrompTugal.dinis |
| Collector | sources/enisa-pubs/collect.mjs |
| Since | 2026-11-18 |
| Last read | 2026-11-21 07:06 UTC |
| Last run | ok: 1 requests ok, 0 failed |
| Now | 10 publications |
| Licence | The data: ENISA legal notice (reproduction authorised with the source acknowledged) (ENISA). This page, the card and the records we add: CC BY 4.0. |
Reuse terms
ENISA legal notice 1.2: reproduction of material on its website is authorised if the source is acknowledged, unless stated otherwise; the logo only for press and media use with the source acknowledged. robots.txt allows /publications to our agent and asks for a 10 second crawl delay; it blocks named AI crawlers (we are code, no model, and not named). Dinis decided on 18 Nov 2026 that ENISA is read through its published interfaces. Not reviewed by a person. Reuse: yes: title, date and link, with ENISA named as the source; no logo; no report text or images.
Reproduction of ENISA material published on this website is authorized, provided the source is acknowledged, unless it is stated otherwise.
Open question: Decided by Dinis on 18 Nov 2026 (about 23:40 UTC): reading is in order. The robots.txt still blocks named AI crawlers; this collector is plain code that reads one page, uses no model and is not named. A person may still want to confirm it with ENISA.
2. The raw data
The raw file is ENISA's publications page as served (HTML, about 80 KB), kept in the vault copy and not served here: the page.
3. The processed data
ENISA has no feed, so the collector reads the first page of its publications list once (robots.txt allows it; ten seconds crawl delay respected; ENISA is read through its published pages and APIs, by Dinis's decision of 18 Nov 2026) and keeps each item's title, date, link on enisa.europa.eu and topics. Source: ENISA. The result: latest.json.
ENISA's newest publications by date, with their topics. The data: /api/v1/enisa-pubs/latest.json.
More about this source
What runs by code, by agents and by people
Code
- the collector reads ENISA's publications page and keeps title, date, link and topics of each item
- GitHub Actions runs it and deploys the site
Agents
- data.b@PrompTugal.dinis wrote the collector and card on 18 November 2026, at cyber.b@PrompTugal.dinis's request; terms read the same day by data.b.dev@
People
- Dinis Cruz decided the cyber signals on 18 November 2026 (board/guidance/2026-11-18-people-blogs-cyber-and-simulated-payments.md); no person has checked the values (not reviewed); Dinis Cruz decided on 18 November 2026 (about 23:40 UTC) that ENISA is read through its published interfaces
Cost
| Field | Value |
|---|---|
| per run tokens | 0 |
| per run model cost usd | 0 |
| runner | GitHub Actions on a public repository: no charge; one request a run (about 80 KB) |
| build tokens | not measured |
| note | Code only: no model is called when the data is collected. |
API addresses
These addresses stay for the life of v1 (the contract).
curl -s https://data.promptugal.news/api/v1/enisa-pubs/latest.json
curl -s https://data.promptugal.news/api/v1/enisa-pubs/reads.json | head -c 600
Vault
Vault not yet created. The collector writes the bytes of each read to a vault copy; until the vault exists they are not kept.
Last runs
| Time (UTC) | Requests ok | Requests failed | Reads with changed bytes |
|---|---|---|---|
| 2026-11-21 07:06 UTC | 1 | 0 | 0 of 1 |
| 2026-11-20 18:06 UTC | 1 | 0 | 1 of 1 |
| 2026-11-20 07:07 UTC | 1 | 0 | 1 of 1 |
| 2026-11-19 18:05 UTC | 1 | 0 | 1 of 1 |
| 2026-11-19 12:06 UTC | 1 | 0 | 1 of 1 |
| 2026-11-19 06:06 UTC | 1 | 0 | 1 of 1 |
| 2026-11-18 23:59 UTC | 1 | 0 | 1 of 1 |
Showing 7 of 7 runs kept. Full detail with sha256: reads.json.
Preview of the values
The first 5 of 10 entries in publications, as read 2026-11-21 07:06 UTC. Source: https://www.enisa.europa.eu/. Long values are shortened here; the file has them whole.
| title | date | url | Source |
|---|---|---|---|
| CRA-Module B and H: CABs accreditation for notification | 2026-11-16 | https://www.enisa.europa.eu/publications/cra-module-b-and-h-cabs-accreditatio... | source |
| Joint Advisory on the Use of Frontier AI Models for Code Review | 2026-11-12 | https://www.enisa.europa.eu/publications/joint-advisory-on-the-use-of-frontie... | source |
| 2026 Report on the State of Cybersecurity in the Union | 2026-11-10 | https://www.enisa.europa.eu/publications/2026-report-on-the-state-of-cybersec... | source |
| ENISA Technical Advisory on Secure Update Mechanisms | 2026-11-04 | https://www.enisa.europa.eu/publications/enisa-technical-advisory-on-secure-u... | source |
| ENISA Technical Advisory for Software Bill of Materials | 2026-10-22 | https://www.enisa.europa.eu/publications/enisa-technical-advisory-for-softwar... | source |