PHP 8.6 is released: what to check before a production upgrade
PHP 8.6.0 became generally available on 19 November 2026. Review compatibility, extensions and deployment steps before you move a production website.
Read the articleCYPEE Cyber · Field notes
Clear explanations for the people responsible for business websites, applications and infrastructure. Read about assessment scope, common weaknesses and the work that follows a finding.
PHP 8.6.0 became generally available on 19 November 2026. Review compatibility, extensions and deployment steps before you move a production website.
Read the articlePractical reading for planning and improving security work.
WordPress 7.2 RC1 is for testing, not production. Use a private staging copy to check themes, plugins, accessibility and PHP compatibility before the planned release.
Read article
NIST published a draft revision of its OT security guide in September 2026. Here are the proposed changes and how plant teams can review them without treating a draft as a rule.
Read article
Project Zero announced a fixed disclosure deadline that will shorten over time. Product teams should plan for faster triage, fixes, rollout and customer communication.
Read article
Recent research shows that automated systems can find and reproduce software flaws at scale. Defenders still need careful validation, safe disclosure and a reliable repair process.
Read article
India notified the Digital Personal Data Protection Rules in November 2025 with staggered start dates. Use the official timeline to plan data, access and incident processes.
Read article
CERT-In directions require covered organisations to report specified cyber incidents within six hours of noticing them. Prepare contacts, logs and decision roles in advance.
Read article
Cloud access belongs to people, applications and workloads. Review each identity, restrict permissions and monitor token use across cloud and SaaS systems.
Read article
A vendor release protects users only after the update reaches their systems. Track exposure, testing, rollout and verification as one patch process.
Read article
A dependency review should cover ownership, support status, update speed and the path from source to production. Keep the process small enough to repeat.
Read article
A software bill of materials lists components in a product. Keep it current, connect each component to an owner and know how to act when a new advisory appears.
Read article
Build systems can publish code, packages and infrastructure changes. Restrict who can change the pipeline and protect its credentials and artifacts.
Read article
API keys and passwords can remain in Git history after a file is edited. Scan before commit, revoke exposed credentials and review access to affected systems.
Read article
Review input handling, permissions, secrets, logs and failure paths in each high-risk code change. Focus on how the change affects a real user action.
Read article
Source code testing, runtime testing and penetration testing answer different questions. Choose a check based on what you need to learn and when you need the evidence.
Read article
Public error pages should not reveal stack traces, database details or secrets. Keep enough protected logging for engineers to investigate failures.
Read article
Debug output can expose code paths, configuration and sensitive values. Use a private test environment for detailed diagnostics.
Read article
Password recovery can bypass normal sign-in controls. Limit reset requests, protect recovery links and notify users about important account changes.
Read article
Secure, HttpOnly and SameSite cookie settings reduce common session risks. Check the actual production response and scope each cookie to its purpose.
Read article
A browser can send a request with a user’s existing session. Use framework protections and test sensitive actions from an untrusted site context.
Read article
Cross-site scripting occurs when untrusted input reaches a browser as active content. Use context-aware output encoding and safe rendering methods.
Read article
Build database queries with prepared statements or safe ORM methods. Validate inputs and avoid granting the application account broad database permissions.
Read article
A server-side request forgery flaw can make an application contact an unintended destination. Use strict destination rules and block access to internal services.
Read article
A file upload feature handles untrusted data. Restrict size and type, store files outside executable paths and control who can retrieve them.
Read article
Cross-origin resource sharing is a browser access rule, not authentication. Avoid wildcard origins for private data and review credentialed requests carefully.
Read article
Use named keys, narrow permissions and a staged rotation plan. Revoke old keys after dependent systems move to the replacement.
Read article
A GraphQL endpoint can expose many operations through one route. Apply authorization to objects and fields, and limit query cost and depth.
Read article
A webhook endpoint accepts requests from another service. Verify each message, reject replays and handle duplicate deliveries safely.
Read article
Old API versions can remain reachable after a product change. Track routes, owners and retirement dates across production, staging and partner systems.
Read article
Set limits by identity, action and resource cost. Add clear responses and monitoring so controls slow abuse without breaking normal work.
Read article
A plugin needs an owner, a reason to remain installed and a plan for security updates. Remove extensions that no longer support the site.
Read article
Protect administrator accounts with individual users, strong sign-in controls and careful recovery settings. Review who can publish code or install plugins.
Read article
A staging site can reveal unpublished pages, customer records or working credentials. Restrict access and remove production secrets from test copies.
Read article
XML-RPC supports some integrations and remote publishing. If the site does not need it, restrict or disable it through a supported method.
Read article
Review PHP settings that affect errors, file access, sessions and uploads. Apply changes through the host or pool configuration and verify the active runtime.
Read article
Limit SSH access to named people and approved paths. Protect keys, remove stale accounts and monitor administrative logins.
Read article
Unsupported operating systems and runtimes may stop receiving security fixes. Inventory versions, test a migration and remove old public systems.
Read article
Use the smallest set of read and write permissions that keeps the service working. Separate deploy, runtime and secret access where practical.
Read article
A valid certificate is one part of HTTPS. Track expiry, renewal ownership, redirects and every public subdomain that serves the site.
Read article
Every firewall rule should have a purpose, owner and review date. Remove stale temporary rules after confirming they do not support a live service.
Read article
Separate systems by function and business need. Allow only required communication between zones and review the paths that connect them.
Read article
Remote access should use named accounts, strong authentication, approved devices and a clear end date. Review supplier access after each engagement.
Read article
A registrar account can change where a domain sends visitors and email. Protect it with strong authentication, recovery controls and named owners.
Read article
Review storage permissions, public links, identity roles and access logs. A private bucket can become public after a policy change.
Read article
Use trusted base images, remove unused tools and rebuild when important fixes arrive. Scan the image and verify what runs in production.
Read article
Passkeys can reduce password phishing risk when a service supports them. Plan recovery, device replacement and administrator access before rollout.
Read article
These domain controls help receiving systems assess whether mail is authorised. Inventory every sender before you enforce a strict DMARC policy.
Read article
A compromised mailbox or lookalike address can request a false bank change. Confirm payment instructions through a known, separate contact path.
Read article
A short scenario can reveal missing contacts, unclear authority and recovery gaps. Practise the decisions your team may need to make under time pressure.
Read article
Build an authorised inventory of domains, addresses, cloud services and public applications. Assign owners and remove assets that no longer need to be online.
Read article
The EU Cyber Resilience Act applies to products with digital elements, with staged obligations. Manufacturers should check scope, reporting duties and support plans.
Read article
A vehicle manufacturer or tier-one customer may ask a supplier to demonstrate information security through TISAX. Confirm the requested scope before preparing.
Read article
There is no single cybersecurity certificate for every exporter. A buyer contract, product rule or regulated supply chain can create specific requirements.
Read article
Operational technology needs safeguards that respect production and safety. Map connections first, restrict remote access and plan checks with the plant team.
Read article
Manufacturers in Ludhiana depend on production systems, supplier networks and customer data. This guide sets out practical controls for factories, workshops and growing exporters.
Read article
Rank security work by exposure, evidence, business impact and the time needed to reduce risk. A clear process helps teams act without treating every alert as equal.
Read article
Use a clear first-response plan to protect people, preserve evidence and restore operations. Do not rush to erase a system before you understand what happened.
Read article
Test what each user can view and change. Do not rely on hidden buttons or hard-to-guess record identifiers to protect business data.
Read article
Keep logs that help answer who did what and when. Protect them from tampering, limit sensitive data and assign someone to review alerts.
Read article
Review users, service identities, access keys and administrative roles across cloud accounts. Confirm each permission has an owner and a business need.
Read article
Review supplier access, data handling, incident reporting and recovery based on the service they provide. Keep the questions tied to business impact.
Read article
Protect email, administrator accounts, remote access and cloud services first. Keep recovery methods under control and test the process with staff.
Read article
A backup is useful only if you can restore the data and systems you need. Test a controlled recovery and record the time, gaps and access required.
Read article
Every public service needs a business reason, an owner and a maintenance plan. Review network exposure from the outside and close access that is not required.
Read article
Start server hardening with ownership, supported packages, restricted access, safe defaults and tested recovery. Keep a record of each change.
Read article
Review identity, object permissions, input limits, error handling and logging before an API goes live. Use test accounts and realistic workflows.
Read article
Use this practical checklist to review site access, updates, forms, backups, hosting and recovery. Assign an owner to each task.
Read article
A vulnerability assessment finds and reviews potential weaknesses. A penetration test investigates selected issues within an agreed scope. Choose the work based on the decision you need to make.
Read article
An API must check whether a user can access each requested record. A hard-to-guess identifier is not an access control rule.
Read article
Prepare an API test by mapping routes, roles, data and business actions. A clear scope helps the test focus on the access rules that matter to your product.
Read article
A repeat compromise often means an access path or vulnerable component remains. Use a calm, evidence-led process to contain the issue and identify what needs to change.
Read article
WordPress 7.1.5 is a security release from 18 November 2026. Update supported sites, check older branches and confirm that the deployed files match the intended version.
Read article
CVE-2026-114938 affects some OpenJDK and Oracle Java environments. The hard part for many teams is finding the Java copies bundled inside products and containers.
Read article
PHP released urgent security fixes on 19 November 2026. Find every PHP runtime, update it through the right vendor, and restart the workers that serve requests.
Read article
Cyber security protects the devices, accounts, applications and information a business relies on. Learn how common threats work, where network security fits and which practical steps to take first.
Read article
A useful assessment starts with the site’s purpose and exposure. Here is what to agree on before testing begins and what a business should expect from the findings.
Read article
Both approaches can support security work, but they answer different questions. Choose based on the system, the decision you need to make and the depth of evidence required.
Read article
Use a repeatable review to check updates, accounts, extensions, backups and recovery. The right controls depend on how the site is hosted and maintained.
Read article