PHP's October security fixes: what small businesses should ask their host
Your website can need a PHP update even when WordPress and its plugins are current. A practical response to the October 21 fixes and October 23 follow-up.
Incident response, identity, cloud security, and the decisions behind the controls.

Your website can need a PHP update even when WordPress and its plugins are current. A practical response to the October 21 fixes and October 23 follow-up.
NGINX may sit between your customers and the application without appearing in your website dashboard. Check ownership, running versions, and the routes that matter to your business.
A certificate-authority incident can affect the software your business trusts as well as the certificate on its website. Check both before Google's announced October 27 root-store change.
The next FedRAMP deadlines matter to cloud providers. The shift toward current, testable security evidence also offers a useful model for smaller businesses that do not sell to government.
A vulnerability count rarely tells an executive what to approve. Build risk entries around business disruption, accountable owners, and decisions that can be revisited.
Use a payroll, sales, or customer-support service to connect governance, protection, detection, and recovery. Build a short current-state review that points to work your team can finish.
Recent AI-related security reporting points to a practical review: what can the application read, which tools can it invoke, and which credentials are exposed if something goes wrong?
NIST's August 2026 draft explores AI-assisted CSF analysis and reporting. Teams can use it to reduce drafting work while keeping evidence, uncertainty, and human approval visible.
Build a patch queue from known exploitation, reachable systems, and business impact. Includes a worked triage example and an exception record.
Define usable AI approval rules around data, connectors, and business decisions, with a sample workflow record and a practical exception process.
Test whether recovery still works when production identity and backup administration are untrusted, with explicit restoration and executive decision checks.
Review supplier accounts, OAuth grants, and service dependencies, then test how access would be removed without losing essential operations.
Protect account recovery and payment approvals against cross-channel social engineering, with a help-desk scenario and concrete verification checks.
Build a cloud and SaaS evidence map around actual investigation questions, with AWS and Microsoft logging caveats and a repeatable collection test.
Review deployed Kubernetes workloads for privilege, network reach, identity, and recoverable evidence, with a safe release-validation exercise.
Trace an event-driven application from trigger to side effect, then test authorization, duplicate delivery, permissions, and failure handling.
A practical first-month security plan for a small team, with weekly evidence checks and a sample control register instead of a policy-writing exercise.
Run a safe restore test that measures usable business recovery, with a worksheet for recovery time, data loss, dependencies, and owner acceptance.
Follow sensitive data through exports, devices, and backups, then check encryption coverage, authorized access, and key recovery.
Start Zero Trust with one business service, test access decisions and alternate paths, and expand only after the controls and support process work.
Write an incident brief that separates confirmed facts from unknowns and gives executives a specific decision, owner, deadline, and next update.
Review effective sign-in policies, recovery, administrator roles, and application access in Okta and Entra ID using controlled positive and negative tests.
Compare MFA methods by phishing resistance, recovery, and deployment needs, without treating number matching or one-time codes as phishing resistant.
Run a ransomware tabletop with concrete injects, evidence requirements, and follow-up tests that distinguish discussion from demonstrated response capability.
Choose log retention by investigation need, compare searchable and archive storage, and test retrieval with a simple cost model and evidence record.
Improve identity lifecycle and access reviews with a mover scenario, explicit policy inputs, and verification of downstream revocation.