Built for rail
Basalt's York practice has been working rail threat profiles long enough to know which controls actually move the dial — and which line items quietly waste budget. We bring that pattern recognition in week one.
York, United Kingdom
Code Security Audit in York.
York rail organisations face OT/SCADA intrusion, signalling-system risk and ticketing fraud. Basalt's code security audit practice tests against that real threat profile, not a generic United Kingdom-wide playbook. Manual and tooled code review across your highest-risk repos — secrets, auth, injection, deserialisation and supply-chain risk, with CI integration that keeps findings from coming back.
85% of findings ship with a working patch suggestion — across Basalt operations in the past 12 months.
THREAT VECTOR
Threats facing York rail.
The rail, tourism, research concentration around York sees OT/SCADA intrusion, signalling-system risk and ticketing fraud. Our code security audit work in Yorkshire is scoped against this real threat profile, not a generic checklist.
Common pains
- Tools that report thousands of low-quality findings
- No clear ownership for fixing vulnerabilities in code
- Supply-chain risk in third-party dependencies
ENGAGEMENT
How we engage.
- Manual review of high-risk code paths
- SAST + SCA integrated into CI with quality gates
- Threat model per service or repository
- Developer-grade fix guidance with sample patches
Reporting
Every finding ships with a control reference against NCSC Cyber Assessment Framework and UK GDPR, with NCSC UK guidance cited where it changes the remediation priority. Board reporting follows the FCA SYSC operational resilience expectation set.
LOCAL CONTEXT
Local context.
Basalt delivers code security audit to organisations across York and the wider Yorkshire region (population ~210k). The rail, tourism, research sectors that anchor the region face a distinct threat profile — OT/SCADA intrusion, signalling-system risk and ticketing fraud — and our engagements are scoped to that, not a generic playbook. Reporting maps cleanly to the NCSC Cyber Assessment Framework and UK GDPR that British boards already use, with regulator context (NCSC UK) called out where it changes a remediation priority.
RATIONALE
Why Basalt for code security audit in York.
Reporting that lands
Findings ship with control references against NCSC Cyber Assessment Framework and UK GDPR and remediation guidance written for the team that has to action it. Your board, your auditor, and your on-call engineer all get something they can use.
No vendor bias
Basalt doesn't resell tooling. British rail clients get an independent read on what's working, what isn't, and what's costing more than it should — not a thinly-veiled sales pipeline.
2026 THREAT LANDSCAPE
What we test for.
- Agentic AI tool-abuse and indirect prompt injection at scale
- MCP server and AI-tool supply chain compromise
- Post-quantum cryptographic readiness (NIST PQC migration)
- Identity-first attack chains across federated SaaS
- Open-source software supply chain (post-xz, post-tj-actions)
Cyber security in United Kingdom can't be done with last year's threat models. The Basalt practice runs against current attacker tradecraft — agentic AI abuse, MCP and AI-tool supply chain, post-quantum readiness — alongside the legacy infrastructure work that still keeps most organisations awake at night.
FAQ
Frequently asked questions.
How fast can Basalt start a code security audit engagement in York?
Most York engagements scope inside one week and start within two. Retainer clients can trigger work the same day. We do not pipeline British clients through junior teams — a senior consultant scopes and runs the work end-to-end.
Do you do code security audit on-site in York or remote?
Both. Sensitive work — classified-adjacent environments, live incident response, OT walkthroughs — gets on-site time in York and the wider Yorkshire region. Routine assessments and detection engineering run remote with a tight feedback loop.
How does Basalt map findings to British regulators?
Every finding ships with a control reference against the NCSC Cyber Assessment Framework and UK GDPR so your compliance team is not re-mapping our report. Where NCSC UK guidance exists for the specific finding, we cite it inline. Board-level reporting follows the FCA SYSC operational resilience expectation set.
What makes code security audit in York different from a generic engagement?
The rail sector concentration in York drives a different threat model than a generic British engagement — OT/SCADA intrusion, signalling-system risk and ticketing fraud. Our scoping reflects that, and so does the test library we bring to the work.
Is Basalt set up for AI-era threats, not just legacy infrastructure?
Yes — this is core to how we work. Basalt actively researches and tests against agentic AI tool-abuse and indirect prompt injection at scale, MCP server and AI-tool supply chain compromise and identity-first attack chains across federated SaaS. Most regional providers haven't mapped these attack paths; we run them in production against client systems with explicit scope.
RELATED OPERATIONS
Other operations in York.
Cyber Security Consulting in York
Strategic cyber security consulting
AI Red Teaming in York
Adversarial testing for LLMs and AI systems
Penetration Testing in York
CREST-aligned penetration testing
Identity Threat Detection & Response in York
ITDR for identity-driven attacks
OTHER DEPLOYMENTS
Code Security Audit in other United Kingdom cities.
Code Security Audit in LondonCode Security Audit in ManchesterCode Security Audit in BirminghamCode Security Audit in LiverpoolCode Security Audit in LeedsCode Security Audit in SheffieldCode Security Audit in BristolCode Security Audit in Newcastle upon TyneCode Security Audit in EdinburghCode Security Audit in GlasgowCode Security Audit in CardiffCode Security Audit in Belfast