Cybersecurity credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The surface
Six ways in, one place the work happens
An estate is attacked through whichever of these is weakest, and defended through the same programme regardless of which one it was.
Six exposure surfaces — applications, APIs, cloud, identity, network, third parties — converging into assessment, remediation and monitoring, producing actionable findings, closed gaps, working detection and evidence for customers.
Applications
Web and mobile, including the ones a business unit commissioned without telling anyone.
APIs
The largest and least reviewed surface in most estates, because the consumers are machines.
Cloud
Configuration, identity and the project account nobody owns.
Identity
Standing privilege, service credentials, and accounts that outlived their owner's employment.
Network
Flat segments, forgotten remote access, and the link into an operating environment.
Third parties
Suppliers with access into the estate, and the subcontractors behind them.
What we do
Assess, fix, keep watching
Testing scoped from the estate rather than from a product list, remediation done by the same engineers who found the finding, and detection that reaches a person who can act at three in the morning.
A finding you can act on
Reproduction steps, the business consequence, and a fix — not a severity rating and a CVE list.
A closed gap
Remediation delivered and retested, rather than a report handed to a team with no capacity.
Detection that fires
Alerts tested against the techniques that would actually be used on your estate.
Evidence for the customer
The artefacts an enterprise buyer or an assessment asks for, produced as a by-product of the work.
The order in the left column is not a priority list. Which surface matters most is a property of your estate, and establishing that is the first week of an engagement rather than an assumption in a proposal.
The starting point
Most organisations do not have a security problem they can name
They have an assessment coming, a customer requirement they cannot evidence, or a suspicion that the estate has grown faster than the controls over it. All three produce the same underlying question: what is actually exposed, and how would anyone know if something happened?
The answer is rarely more tooling. Security products accumulate the way applications do, and an environment running four overlapping tools with nobody reading the output is less defensible than one running two that somebody acts on. The useful work is establishing what exists, reducing what is unnecessary, and making what remains produce evidence a person uses.
In Saudi Arabia there is a second half to the question. Whatever you do has to be demonstrable to somebody else — an NCA assessment, a Saudi Central Bank review, an Aramco supplier audit, or a customer passing down their own obligations. That changes the deliverable. A finding is not closed when the engineer says so; it is closed when there is a record showing what changed, when, under whose approval, and that the fix was retested.
Capabilities
What we actually do
Assessment and gap analysis
Technical assessment of the environment, mapped against whichever control set binds you. The output is a prioritised finding list with an owner, an effort estimate and the evidence each fix will need to produce.
Penetration testing and VAPT
Web applications, APIs, mobile applications, internal and external networks, and cloud configuration — reported with reproduction steps and business impact rather than a scanner export with severity labels attached.
Remediation engineering
Segmentation, identity and access, hardening, logging, key and secret management. We would rather fix the findings than hand over a report and leave — an assessment without remediation capacity tends to sit until the next assessment finds the same things.
Detection and monitoring
Log collection, detection rules written against your environment rather than a vendor default set, and alert tuning so the daily volume is something a real team can work through without learning to ignore it.
Operating technology and industrial security
Passive asset discovery, protocol-aware monitoring, segmentation between plant and corporate networks, and brokered vendor remote access. Planned around the maintenance calendar, because a control that is routine in an office can stop a production line.
Compliance evidence
Assembling the documentation, log retention and change records an assessor asks for, and leaving behind a process so the next cycle does not start from nothing when the original project team has moved on.
Control sets
Which requirement applies to you, and what it needs from the engineering
The first useful piece of work on most Saudi engagements is establishing which of these actually binds you. Several often do, and they do not ask for the same evidence.
NCA ECC — you are a government entity, or a private operator of critical national infrastructure
Mapping the estate to the published control set, closing the technical gaps, and putting governance behind the controls that need an owner rather than a configuration change.
Evidence produced: Control-by-control status, remediation record, evidence pack
Aramco SACS-002 — you supply Saudi Aramco, or subcontract to one of its suppliers
Scoping the in-scope environment against your classification, closing technical findings, and assembling the self-assessment package an Authorized Audit Firm will validate.
Evidence produced: Scoped control status, remediation evidence, submission package
SAMA Cyber Security Framework — you are a bank, insurer or payment firm under Saudi Central Bank supervision
Resilience and third-party risk work: tested recovery procedures, a dependency map that reflects the current system, and controls over the suppliers who touch it.
Evidence produced: Recovery timings, dependency map, supplier assurance records
PDPL — you process personal data of individuals in the Kingdom
Finding where personal data actually sits, restricting access to it, and building the retention and deletion behaviour the system is supposed to have.
Evidence produced: Data inventory, access model, retention behaviour
How an engagement runs
Scope, test, fix, prove
Scope
Agree what is in scope, what is off limits, the testing window and what a finding has to look like to be actionable. Written scope and rules of engagement.
Assess
Technical assessment and testing, run to the agreed rules. Anything that could disturb a live process is scheduled with your operations team, not decided by the testers.
Report
Findings with reproduction steps, business impact and a remediation plan ordered by what reduces risk fastest for the effort.
Remediate
Fix the findings, with your team or as an engineering workstream we run alongside them.
Verify
Retest what was fixed. Closure is evidenced, not asserted — which is also what an assessor will want to see.
Operate
Monitoring and periodic reassessment, or handover to your team with the runbooks to do it themselves.
What this looks like
A typical first engagement
Illustrative — not a named client
A Riyadh services group is told by its largest customer that it must evidence its security controls within a quarter. It runs about forty internal applications, two cloud accounts nobody has fully inventoried, and a network that grew through three acquisitions.
- 01Two weeks establishing what is actually connected — cloud accounts, external surface, identity paths — before any testing, because the estate as documented and the estate as running are different.
- 02Testing concentrated on the internet-facing applications and the identity layer, because that is where a real intrusion would start, rather than spreading thin across forty applications.
- 03Remediation run as a joint workstream: their team took the application fixes, we took segmentation, logging and the cloud identity model.
- 04Retest of the closed findings, and an evidence pack assembled as the work happened rather than reconstructed at the end.
The customer requirement was met on evidence rather than assertion, and the group kept a documented asset inventory it did not have before — which is usually the more durable result.
Working surface
Environments we work across
Cloud
- AWS
- Microsoft Azure
- Kubernetes
- Terraform
Identity
- Entra ID
- Active Directory
- SAML / OIDC
- Privileged access
Detection
- Splunk
- Elasticsearch
- Cloud-native logging
- Custom detections
Industrial
- Passive discovery
- Protocol-aware monitoring
- Segmentation
- Brokered access
Common questions
What buyers ask
How long does a penetration test take?+
For a single web application or API, typically one to two weeks of testing plus reporting. A network or multi-application scope runs longer. Scope size is the variable that matters most, so we would rather agree a precise scope than quote a duration against a vague one.
Can you test without disrupting live systems?+
Yes, with planning. Anything carrying disruption risk is scheduled in an agreed window with a rollback and an operations contact on call. In industrial environments we default to passive techniques and treat any active step as a change requiring approval. If a test cannot be made safe, we say so and find another way to get the evidence.
Do you help fix findings, or only report them?+
Both are available and we usually recommend the first. Where your team will do the fixing, we support them and retest. Where they do not have capacity, we run remediation as an engineering workstream. A report with no route to closure rarely improves anything.
Is Techbanq certified or accredited by the NCA?+
No, and no consultancy should describe itself that way. The NCA publishes control sets and supervises entities against them; it does not accredit consultancies to deliver compliance. What we do is assess you against the published controls, close the technical gaps and assemble the evidence. The assessment outcome rests with your entity and its assessors.
What do you need from us to start?+
A scope definition, written authorisation to test, technical contacts, and — for authenticated testing — test accounts at the privilege levels you want covered. For industrial environments we also need the maintenance calendar and an operations contact before anything active happens.
In this cluster
Next step
Request a scoped assessment
A scoping call that ends with a written scope, a rules-of-engagement draft and a fixed testing window. One hour, no cost, no commitment.
