Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The transmission
How a government entity's obligations become its supplier's obligations
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
A government entity cannot discharge its cybersecurity obligations by outsourcing the systems they attach to. When your platform processes its data, hosts its service or connects to its network, the entity remains accountable for that data and that service — so its only lawful posture is to require of you what is required of it, in the contract, and to verify you meet it. The security annex in the tender is not the procurement team being cautious; it is the entity's own compliance, flowing downstream.
This explains two things suppliers find puzzling. First, why the requirements look like a national framework rather than a bespoke list: the client is passing through obligations it reads from the Authority's published control sets, so your annex tracks that text. Second, why the client's security team can be harder to satisfy than the evaluation committee: the committee scores your bid once, while the security team inherits your posture for the life of the contract, and audits accordingly.
The evidence
What a government client's security team asks a technology supplier to show
The requests vary by entity and by what you will hold, but they cluster into a small set of families. Each row is something you can prepare once, before any specific tender names it.
Governance and policy set
That security has an owner and written rules at your organisation, not a folder created for this bid.
What you prepare in advance: Current, dated policies with an accountable role behind them.
Access and personnel answers
Who at your company will be able to touch the entity's data and systems, how that access is granted, reviewed and ended.
What you prepare in advance: A written access model with joiner, mover and leaver evidence.
Hosting and data handling
Where the entity's data would live, what protects it there, and who else could reach it — including your own cloud providers.
What you prepare in advance: A data-flow account per service, with your providers' halves referenced.
Incident handling and continuity
That an incident touching the entity's data would be detected, contained and reported to the client — not discovered by the client.
What you prepare in advance: An incident process with notification duties written into it.
Timing
Aligning posture before the tender instead of after the award
The security annex is knowable before any tender names you, because it flows from published frameworks. That makes alignment a calendar choice, and the calendar strongly favours early.
A four-step path — reading the published frameworks as a supplier, assessing posture against them, closing gaps and filing evidence, bidding with answers attached — with a branch for obligations that surface after award.
- 01
Read the frameworks as a supplier
Before any tender, the Authority's published control sets tell you the shape of what government clients will require of the systems and data you would hold.
- 02
Assess your posture against that shape
An honest internal reading finds the gaps a client security review would find — while there is still time to close them off the tender clock.
- 03
Close the gaps and file the evidence
Remediation done calmly, with the evidence indexed as it is produced, so the security annex is answered from a folder rather than from a war room.
- 04
Bid with the answers attached
The bid carries the security answers as prepared artefacts, and the delivery plan starts at delivery — not at remediation the client is now watching.
A requirement surfaces after award
Some obligations only crystallise in contract negotiation. The prepared supplier absorbs them as deltas on an aligned posture; the unprepared one renegotiates its delivery timeline in its first month.
Flow-down
Passing the obligations to your own subcontractors before they surprise you
The same mechanism that carried the entity's obligations to you carries yours to whoever you bring onto the contract. If a subcontractor hosts a component, holds credentials or processes the entity's data, its posture is now part of yours — and the client will treat any failure there as your failure, because contractually it is. The flow-down is not optional courtesy; it is the only way your own commitments remain true.
Practically, that means three clauses and one habit. The clauses: your subcontracts mirror the security obligations of the prime contract, name the evidence the subcontractor must maintain, and give you the right to verify. The habit: you actually verify — at onboarding and on a cadence — because a clause nobody checks is the exact paper posture the client's security team is trained to detect. Suppliers who manage this well often find it becomes a selection filter of its own: the subcontractors who can answer are the ones worth building a government practice with.
Our role
How we ready a government supplier, and where the client entity decides
- 01
Reading the annex against reality
We map a tender's security requirements to the published frameworks they descend from and to your actual estate, so you know before bidding which asks you meet, which you can close in time, and which should shape your bid.
- 02
Closing the gaps off the clock
Posture work — governance, access, logging, incident handling — is delivered with your teams before a live bid depends on it, with the evidence indexed as it is produced.
- 03
Building the reusable answer set
The security responses, the data-flow accounts and the subcontractor flow-down pack are written once and versioned, so each new tender starts from the last one's answers rather than from a blank annex.
Which requirements a given contract carries, and whether your posture satisfies them, are the client entity's determinations under its own obligations — what we prepare is a supplier who meets that review with written answers and operating controls behind them.
The obligations government clients pass downstream descend from the control sets the National Cybersecurity Authority publishes. Read the published text, and take questions about what applies to a specific contract to the client entity and the Authority. Source
Common questions
What buyers ask
The tender documents barely mention cybersecurity. Can we treat it as out of scope?+
Treat it as deferred, not absent. A thin annex usually means the security requirements arrive later — in clarifications, in contract negotiation, or as the client security team's conditions before go-live — because the entity's own obligations do not disappear when its procurement template is brief. The suppliers hurt worst by this pattern are the ones who priced and planned as if silence meant exemption. Bid on the assumption that the published frameworks will reach you through this contract as they do through every other, and price the posture work in.
We won a government contract and the security requirements landed afterwards. What is the recovery order?+
First, get the requirements in writing and mapped — to the published framework text where they descend from it, and to your estate — because negotiating or scheduling against a vague list compounds the problem. Second, agree a remediation plan with the client's security team before they discover the gaps themselves; a supplier who tables its own honest plan keeps control of the sequence. Third, close the items that gate the client's data first — access, hosting, logging — since those decide when delivery can actually start. The lasting fix is to fold what this contract taught you into a standing posture, so the next award does not repeat the scramble.
Do subcontractors on our government project inherit our cybersecurity obligations automatically?+
Not automatically — and that is precisely the risk. Your obligations to the client bind you regardless of who actually operates the component, but they only reach your subcontractor through your subcontract. If that document is silent, you have promised the client controls you have no contractual means to demand, and the gap is yours alone. The flow-down therefore has to be deliberate: mirror the security obligations into the subcontract, name the evidence the subcontractor maintains, keep a right to verify, and use it. Check the prime contract too — some government contracts constrain subcontracting itself, or require the client's approval of who you bring in.
In this cluster
Next step
Align before the next tender
A supplier whose posture, documents and answers are ready before the tender closes — so the security annex is a checklist you meet, not a discovery you absorb after award.
Align before the next tender
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
