- 01
Market
Saudi Arabia
- 02
Written for
CTO, Founder, Commercial Director
- 03
Decision
Meet Aramco supply-chain cybersecurity expectations as a software product vendor, without rebuilding the answer per customer
- 04
Languages
EN · AR
Credentials for Aramco compliance
NCA registration
Registered cybersecurity service provider

Aramco CCC
CCC certified

ISO/IEC 27001
ISO/IEC 27001 certified
The mapping
How a software product acquires third-party cybersecurity expectations
The expectations attach to what the relationship touches, not to your job titles. Walk your own product down this path and you will know roughly where you stand before anyone asks.
A path showing how expectations attach to a software product: the data it receives, where it runs, what its update path can carry, and what the contract then requires — with a branch for unclear cases, which go to Aramco's published material rather than to guesswork.
- 01
What the product receives
Drawings, operational data, personnel records, telemetry — whatever customer material enters your software or your company decides the sensitivity of the relationship.
- 02
Where the product runs
Software inside the customer's network, a cloud service you host, or an offline tool each carry different expectations — connectivity and hosting change what you must answer for.
- 03
What the update path can carry
A vendor who ships releases into a customer estate holds a standing channel into it. Buyers now ask how that channel is secured, because supply-chain incidents taught everyone what an update can deliver.
- 04
What the contract then requires
The classification and the obligations are settled by Aramco's published material and your contract — the earlier nodes predict them; the paperwork pronounces them.
When the mapping is unclear
A product that fits no category cleanly is a question for Aramco's published material and your customer's procurement — not a judgement to improvise. Raising it early costs a conversation; guessing wrong costs an audit finding.
The evidence
The secure development record a supply-chain buyer asks a software vendor for
When a buyer in this ecosystem reviews a software vendor, its questions concentrate on the life of the code rather than the perimeter of the office: how changes are reviewed before they merge, how third-party dependencies are chosen, tracked and updated, how a release is built and signed so the customer can trust that what arrives is what you shipped, and what happens — concretely, with named duties — when a vulnerability is reported in your product. None of these questions is answered by a firewall diagram, which is why vendors with tidy infrastructure and no development record still stall in review.
The good news is that this evidence is cheapest to produce where it should come from anyway: the development pipeline. Review records, dependency inventories, build provenance and vulnerability tickets are all by-products of a pipeline configured to keep them — which means the gap, for most vendors, is not new engineering practice but the discipline of retaining and indexing what the practice already generates. A vendor who sets that up once holds an account of its software's integrity that improves with every release, instead of a document that decays from the day it is written.
Illustrative engagement
One preparation serving many customers, walked through
Typical engagement — illustrative, not a named client
A product company selling planning software wins its first customer inside the Aramco supply chain. Procurement raises the certificate question and sends a security questionnaire; a second prospect in the same ecosystem sends a different questionnaire the same month. The engineering team is answering both by hand, and the founders can see the pattern: every future deal will repeat this cost.
- 01Map the product once: what customer data it processes, where each deployment model hosts it, what the update channel can carry — the vendor's position in Aramco's published third-party picture, written down.
- 02Wire the development pipeline to retain its own evidence — review records, dependency inventory, build provenance, vulnerability handling — so the assurance pack regenerates with each release instead of being rewritten per deal.
- 03Prepare the certificate position honestly: what the requirement is, per Aramco's published programme, and where the company stands on it — so procurement conversations start from a stated position rather than a promise invented in the meeting.
The third questionnaire is answered from the pack in days, by one person, with engineering consulted only on the delta. The reusable preparation did not remove the customers' reviews — it removed the rebuilding of the answers.
Our role
Where our work for a software vendor ends and Aramco's process begins
- 01
The product map
We document what your software receives, where it runs and what its update path carries, and set that against Aramco's published third-party material — so your obligations are read, not assumed.
- 02
The pipeline evidence
We configure your development pipeline to retain review, dependency, build and vulnerability records as it runs, and assemble them into an assurance pack that regenerates per release.
- 03
The certificate conversation
We prepare your written position on the Cybersecurity Compliance Certificate — what the published programme asks, where you stand, what your readiness plan is — so procurement discussions run on facts your team can state consistently.
The certificate itself is assessed through audit firms Aramco authorises and issued under Aramco's programme, and each customer's procurement makes its own acceptance decision — what we build is the evidence and the position both of those processes will read.
Aramco's supplier pages publish the third-party cybersecurity requirements and the certificate programme, including how the assessment is obtained. Work from that material, and put classification questions to Aramco and your customer rather than to any consultancy. Source
Common questions
What buyers ask
We sell licences and never touch operations. Do Aramco's third-party expectations still reach a pure software vendor?+
They can, because the expectations follow the relationship's exposure rather than your delivery model. A licensed product that processes the customer's engineering data, authenticates its users, or receives updates from you carries exposure a buyer must account for, whoever operates it day to day. What genuinely changes for a pure software vendor is the shape of the questions — less about your facilities, more about your development lifecycle, release integrity and vulnerability handling. Whether the certificate requirement itself applies to your specific relationship is settled by Aramco's published material and the contract, and it is worth establishing early rather than mid-procurement.
Which secure development evidence can a software vendor prepare before any customer asks for it?+
Four artefacts cover most of what reviews request, and all four can exist before the first questionnaire. A dependency inventory for the product, kept current by the build rather than by hand. Review records showing that changes are examined before they merge. Build provenance — an account of how a release is produced and signed, so a customer can verify what it installs. And a written vulnerability-handling process with named duties, from report to fix to customer notification. Prepared cold, each takes deliberate effort; wired into the pipeline, each becomes a by-product of shipping — which is why we set them up inside the pipeline rather than as documents beside it.
Every buyer's security review looks different. Is preparing once actually realistic for a software vendor?+
Realistic for the core, which is most of the volume. The questionnaires differ in format and ordering far more than in substance: underneath, they ask the same things — what data you hold, how the software is built and released, who can access customer environments, what happens on a vulnerability. A maintained pack answers that shared core immediately, every time. What preparation cannot remove is each buyer's specific tail — a clause its regulator requires, a format its platform demands — and, separately, any formal assessment such as the certificate audit, which runs on its own process regardless of your pack. The honest promise of preparing once is that each review costs a delta instead of an engagement, and that is usually the difference between sales owning the process and engineering being interrupted by it.
In this cluster
Next step
Prepare the vendor evidence once
A software vendor with one maintained assurance pack — product map, secure development evidence, certificate position — that answers the next procurement security review without pulling engineers off the roadmap.
Prepare the vendor evidence once
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
