PHP.1
The Canonical Identity & Security Layer for PHP Infrastructure
Identify • Assess • Fix • Verify • Monitor
PHPFix.Team
AIEndpointsRegistry
PHP Security Passport
SafeAI Assurance
Why PHP Infrastructure Needs an Identity Layer
PHP powers a vast proportion of the web. But when a critical vulnerability emerges, the fundamental question for an organisation is not simply: “Is PHP vulnerable?”
It is: “Where are we running PHP, which versions are we running, who is responsible for them, what needs to be fixed, and has the remediation actually been verified?”
The Fragmented PHP Estate
Modern organisations rarely have a single PHP installation. They manage complex, distributed environments comprising:
E-Commerce Platforms
WordPress & Drupal
Joomla Applications
REST & GraphQL APIs
PHP-FPM Environments
Apache / mod_php
Containers & Cloud Workloads
Legacy & Outsourced Hosting
Real-World Case: Critical RCE Disclosures
On 21 October 2026, the PHP project disclosed two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, capable of unauthenticated remote code execution. Security versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 were urgently released.
European cybersecurity authorities advised organisations to identify affected PHP applications, coordinate with hosting providers, and prioritise internet-facing systems. This demonstrates the exact visibility and remediation challenge PHP.1 addresses.
Operational Division of Responsibilities
From Vulnerability Alert to Verified Remediation
PHP.1 transforms slow, manual vulnerability response into a structured, machine-executable Agentic workflow.
The PHP.1 Agentic Workflow
Alert & Discovery
Vulnerability announced → PHP.1 identifies potentially affected identities → Discovery Agent inventories installations.
Assessment & Prioritisation
Vulnerability Agent assesses exposure → Risk Agent prioritises internet-facing and critical business systems.
Remediation & Execution
PHPFix Agent creates plan → Patch/Upgrade Agent executes approved remediation under human oversight.
Verification & Assurance
Testing Agent verifies operation → Verification Agent records evidence → Monitoring Agent maintains surveillance.
The PHP Security Passport
Each PHP.1 identity maintains a persistent, machine-readable PHP Security Passport containing evidence across six core infrastructure layers:
| Passport Section | Attribute Records & Machine-Readable Data |
|---|---|
| Identity | PHP application identity, organisation, domain, infrastructure operator, hosting provider, environment, jurisdiction. |
| Runtime | PHP version, PHP-FPM / Apache / CGI runtime, operating system, container, framework, CMS, extensions. |
| Security | Known vulnerabilities, affected components, CVE references, severity, exposure level, remediation status, compensating controls. |
| Lifecycle | Supported status, security-only support, approaching EOL, EOL state, migration requirements. |
| Evidence | Scan date, patch date, test results, verification evidence, responsible Agent, human approval record, last review. |
| AI Endpoint | Canonical AI identity, capabilities, interaction endpoint, security Agents, monitoring Agents, responsible human lead. |
PHPFix.Team — Specialist AI Agent Team
PHPFix.Team operates as a dedicated Agent Team within the wider AI Endpoints ecosystem, executing 10 distinct operational roles:
| Agent Role | Operational Function & Capability |
|---|---|
| 01 — Discovery Agent | Finds PHP-based applications and infrastructure across cloud, container, and on-premise environments. |
| 02 — Inventory Agent | Creates detailed inventories of PHP versions, frameworks, CMS platforms, extensions, and dependencies. |
| 03 — Vulnerability Agent | Maps infrastructure components against live CVE databases and security advisories. |
| 04 — Risk Agent | Prioritises systems according to exposure, criticality, internet accessibility, and business impact. |
| 05 — Lifecycle Agent | Identifies obsolete, unsupported, and approaching-EOL PHP environments. |
| 06 — Remediation Agent | Generates proposed upgrade, patching, or migration actions and configuration scripts. |
| 07 — Testing Agent | Executes automated regression, unit, and functional tests following patch application. |
| 08 — Verification Agent | Records cryptographic evidence that required remediations have been successfully completed. |
| 09 — Monitoring Agent | Continuously monitors the PHP estate for new vulnerabilities, version changes, and lifecycle events. |
| 10 — Human Security Lead | Retains ultimate governance, handling approvals, exceptions, risk acceptance, and policy decisions. |
Federated Architecture & Separation of Powers
Programmatic Architecture Flow
│
AIEndpointsRegistry.com (Discovery & Resolution)
│
PHP.1 (Canonical Infrastructure Identity)
│
PHPFix.Team (Discovery • Assessment • Remediation)
│
SafeAI.software (AI Assurance & Verification Layer)
│
Human Governance (Accountable Oversight)
Separation of Powers Matrix
| Architecture Layer | Defined System Role |
|---|---|
PHP.1 |
Canonical PHP identity and machine-readable state layer. |
AIEndpointsRegistry.com |
Neutral discovery and resolution layer. |
PHPFix.Team |
PHP security, assessment, and remediation Agents. |
SafeAI.software |
Assurance of AI systems, models, and remediation workflows. |
AIAgent.Shop |
Discovery, licensing, and provisioning of specialist Agents. |
Safe-AI.App |
User control, monitoring, and AI management interface. |
SafeAI.IM |
Trusted, encrypted Agent-to-Agent (A2A) communication. |
Selling.center |
Commercialisation, enterprise engagement, and service contracts. |
| Human Operators | Governance, consequential decision approvals, and risk policy. |
Ecosystem & Trade Gateway Integrations
Digital Trade Readiness & Trade Gateways
A Chamber of Commerce operating a .Trade Gateway (e.g. NorthernIreland.Trade) can embed PHP Security Readiness into member Digital Trade Passports:
Commercial Pipeline & Marketplace
Specialist agents are discoverable via AIAgent.Shop, while Selling.center provides the commercial engagement layer connecting identified risks with qualified human-led remediation services.
The PHP Lifecycle Registry
Acts as an active EOL tracking layer. For instance, with PHP 8.2 reaching End-of-Life on 31 December 2026, PHP.1 alerts operators and plans migration paths automatically.
Live PHP.1 Security Status & Vision
Machine-Readable Status Schema
├── Identity: VERIFIED
├── Runtime: PHP 8.5.12
├── Lifecycle: SUPPORTED
├── Security: CURRENT
├── Last Assessment: VERIFIED
├── Monitoring: ACTIVE
├── Responsible Operator: IDENTIFIED
└── Remediation Agent: PHPFix.Team
Identity remains persistent while security status continuously updates dynamically across an asset’s operational life.
The Bigger Infrastructure Vision
Software components, business systems, products, and physical assets need machine-readable identity. PHP.1 applies this model to one of the world’s most widely deployed web technologies.
Identify the infrastructure • Understand the risk • Deploy the right Agent • Verify remediation • Keep humans in control
