PagoPA · Vulnerability Disclosure

PagoPA Vulnerability Disclosure

Vulnerability disclosure

PagoPA publishes a vulnerability disclosure policy for reporting security issues. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CompanyPaymentsGovernmentPublic SectorDigital IdentityInteroperabilityNotificationItaly
Program: security.txt present

Disclosure Policy

Policy
Policy

Security Contact

Contact
mailto:security@pagopa.it

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-11-11'
method: searched
probe: true
source: https://www.pagopa.gov.it/.well-known/security.txt
policy:
- https://www.pagopa.gov.it/security.html
- https://www.pagopa.it/it/responsible-disclosure-policy/
contact:
- mailto:security@pagopa.it
encryption: https://www.pagopa.gov.it/publickey.txt
preferred_languages:
- en
- it
program:
  name: Responsible Disclosure Policy
  type: self-hosted
  platform: null
  rewards: false
  safe_harbor: true
  hall_of_fame: true
sla:
  acknowledgement: 7 business days (evaluation of the report and an expected resolution date)
  disclosure_window: 90 calendar days after notifying pagoPA, unless mutually agreed otherwise
scope:
  in:
  - IO - https://io.italia.it/
  - pagoPA - https://www.pagopa.gov.it/
  out:
  - TLS ciphers, email spam, volumetric attacks, missing web security headers and general "best practices",
    unless an exploit leveraging them is demonstrated
  - denial of service, brute force, aggressive automated scanning, social engineering
evidence:
- source: well-known/pagopa-security.txt
  kind: security.txt
  url: https://www.pagopa.gov.it/.well-known/security.txt
  http_status: 200
  content_type: text/plain
  fields: [Contact, Encryption, Preferred-Languages, Canonical, Policy, Hiring]
  note: >-
    No Expires field. RFC 9116 makes Expires REQUIRED, so the file is served and parseable but not
    strictly conformant. A negative-control path on the same host (/.well-known/zz-neg-control.txt)
    returns 404, so the 200 is a real document, not a soft-200.
- source: https://www.pagopa.gov.it/security.html
  kind: disclosure-policy
  http_status: 200
- source: https://www.pagopa.gov.it/publickey.txt
  kind: pgp-key
  http_status: 200
- source: https://www.pagopa.it/it/responsible-disclosure-policy/
  kind: disclosure-policy
  http_status: 200
  note: Same Responsible Disclosure Policy, served on the corporate site (pagopa.it).
x-evidence:
  fetched: '2026-11-11'
  host_note: >-
    www.pagopa.gov.it (the pagoPA payments platform site) is not one of the hosts the 2026-10-09
    well-known probe covered; added to the record under roadmap#1144.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/pagopa-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.