NCA ECC: six subdomains with an internet-facing half
The National Cybersecurity Authority’s Essential Cybersecurity Controls, ECC-2:2024, set controls for asset inventory, vulnerabilities, penetration testing, threat intelligence, external web applications and third parties. Each has a part an outsider can observe. This page quotes those controls by number and shows the dated record ShadowMap produces for them.
The text
One sequence, repeated in every subdomain
ECC-2:2024 consists of 4 main domains, 28 subdomains, 108 main controls and 92
subcontrols. It applies to
government agencies in the Kingdom of Saudi Arabia (including ministries, authorities, establishments and others) and their affiliated companies and entities (inside and outside the kingdom), as well as all private sector entities owning, operating, or hosting Critical National Infrastructures (CNIs)
.
Its subdomains are written to a pattern. Subdomain 2-10, on vulnerabilities, shows it: four controls, in the order on the right. Subdomains 2-11, 2-13 and 2-15 repeat the same four, and every subdomain on this page ends on a periodic review.
The quotations come from the English text of ECC-2:2024 published by the NCA, read on 18 November 2026.
-
Control 2-10-1
Requirements identified, documented and approved
The first control of the subdomain is a document the entity writes: its requirements for managing technical vulnerabilities. What the external estate contained on the day it was approved is on the record.
-
Control 2-10-2
Requirements implemented
From here the question is whether the control runs. For the internet-facing estate it does so every 24 hours, and each run carries its date and the inventory it covered.
-
Control 2-10-3
The minimum the requirements include
The numbered subcontrols: periodic assessment and detection, classification by severity, remediation by classification. The table below quotes them.
-
Control 2-10-4
Implementation periodically reviewed
A review reads what happened across the period: what was found, when, who owned it and when it closed. That is the record ShadowMap keeps, so the review of the external part starts from dates and not from recollection.
Control by control
Six subdomains, quoted by the NCA’s own numbers
The right-hand column names the ShadowMap capability that produces the record. The line under each row says what the record holds and which part of the subdomain is the entity’s.
| Control | What the Controls say | The record, and what produces it |
|---|---|---|
| 2-1 | Asset Management, objective: “To ensure that the entity has an accurate and updated inventory of assets, including details of all information and technology assets of the entity” | Attack Surface Management |
| The internet-facing part of that inventory, built from a single apex domain and rebuilt every 24 hours, with each difference from your own register dated. Classification and labelling under control 2-1-5 stay with the entity. | ||
| 2-10-3 | “2.10.3.1 Periodic vulnerabilities assessment and detection. 2.10.3.2 Vulnerabilities classification based on their severities. 2.10.3.3 Vulnerabilities remediation based on their classification and the associated cyber risks.” | Attack Surface Management |
| Continuous assessment of the external estate. Each finding is dated when first seen, assigned to an owner and carried to a disposition. Internal systems and patch management under 2.10.3.4 are assessed from inside. | ||
| 2-11-3 | “2.11.3.1 Scope of penetration testing to include all externally provided services (via the Internet) and their technical components, including infrastructure, websites, web applications, smartphone and tablet applications, email, and remote access.” | Continuous Automated Red-Teaming |
| The scope this subcontrol describes is the estate ShadowMap discovers, so the test starts from a current list of externally provided services. Between two tests, Continuous Automated Red-Teaming validates external findings where it is safe and authorised. The penetration test itself is a separate engagement carried out by people. | ||
| 2-13-3 | “2.13.3.5 Collecting and handling threat intelligence feeds.” | Threat Intelligence |
| Actor, malware, vulnerability and indicator data correlated against the technology discovered on your estate, with credentials attributed to your domains reported in one of four states. Reporting incidents to the NCA and sharing with it, under 2.13.3.3 and 2.13.3.4, are the entity’s to do. | ||
| 2-15-3 | “2.15.3.1 Use of web application firewall.” and “2.15.3.3 Use of secure protocols (e.g. HTTPS).” | Attack Surface Management |
| Which external web applications exist, the certificate each presents, and whether an origin server answers for the same application directly, with the firewall out of the path. Architecture, usage policy and authentication under the other subcontrols are reviewed from inside. | ||
| 4-1 | For third parties providing IT or cybersecurity outsourcing or managed services: “4.1.3.1 Conducting a cybersecurity risk assessment and ensuring the availability of risk mitigation controls before signing contracts and agreements” and “4-1-4 Cybersecurity requirements for third parties shall be periodically reviewed.” | Third-Party Risk Management |
| A dated outside-in read of each third party you nominate, available before a contract is signed and repeated for its life. A third party’s systems are observed from the internet and are not tested. Contract clauses under 4-1-2 are the entity’s. | ||
NCA ECC-2:2024 controls and the outside-in monitoring record
2-1
- What the Controls say
- Asset Management, objective: “To ensure that the entity has an accurate and updated inventory of assets, including details of all information and technology assets of the entity”
- The record, and what produces it
- Attack Surface Management
The internet-facing part of that inventory, built from a single apex domain and rebuilt every 24 hours, with each difference from your own register dated. Classification and labelling under control 2-1-5 stay with the entity.
2-10-3
- What the Controls say
- “2.10.3.1 Periodic vulnerabilities assessment and detection. 2.10.3.2 Vulnerabilities classification based on their severities. 2.10.3.3 Vulnerabilities remediation based on their classification and the associated cyber risks.”
- The record, and what produces it
- Attack Surface Management
Continuous assessment of the external estate. Each finding is dated when first seen, assigned to an owner and carried to a disposition. Internal systems and patch management under 2.10.3.4 are assessed from inside.
2-11-3
- What the Controls say
- “2.11.3.1 Scope of penetration testing to include all externally provided services (via the Internet) and their technical components, including infrastructure, websites, web applications, smartphone and tablet applications, email, and remote access.”
- The record, and what produces it
- Continuous Automated Red-Teaming
The scope this subcontrol describes is the estate ShadowMap discovers, so the test starts from a current list of externally provided services. Between two tests, Continuous Automated Red-Teaming validates external findings where it is safe and authorised. The penetration test itself is a separate engagement carried out by people.
2-13-3
- What the Controls say
- “2.13.3.5 Collecting and handling threat intelligence feeds.”
- The record, and what produces it
- Threat Intelligence
Actor, malware, vulnerability and indicator data correlated against the technology discovered on your estate, with credentials attributed to your domains reported in one of four states. Reporting incidents to the NCA and sharing with it, under 2.13.3.3 and 2.13.3.4, are the entity’s to do.
2-15-3
- What the Controls say
- “2.15.3.1 Use of web application firewall.” and “2.15.3.3 Use of secure protocols (e.g. HTTPS).”
- The record, and what produces it
- Attack Surface Management
Which external web applications exist, the certificate each presents, and whether an origin server answers for the same application directly, with the firewall out of the path. Architecture, usage policy and authentication under the other subcontrols are reviewed from inside.
4-1
- What the Controls say
- For third parties providing IT or cybersecurity outsourcing or managed services: “4.1.3.1 Conducting a cybersecurity risk assessment and ensuring the availability of risk mitigation controls before signing contracts and agreements” and “4-1-4 Cybersecurity requirements for third parties shall be periodically reviewed.”
- The record, and what produces it
- Third-Party Risk Management
A dated outside-in read of each third party you nominate, available before a contract is signed and repeated for its life. A third party’s systems are observed from the internet and are not tested. Contract clauses under 4-1-2 are the entity’s.
Continuous compliance
Why a dated record suits the way the ECC is assessed
The Controls say all entities within scope
shall take all necessary measures to ensure ongoing and continuous compliance with these Controls
,
and that the NCA evaluates compliance
through multiple means, such as self-assessment by the entities, periodic reports of the compliance tool, and/or field auditing visits
.
Ongoing and continuous is a statement about every day of the year. ShadowMap rebuilds the external estate every 24 hours from an apex domain and compares each run with the one before. A newly reachable host or a newly opened port is reported on the day it appears, with the date attached, and each finding carries an owner, a disposition and a change history. An entity completing a self-assessment, or preparing for a visit, takes the external controls from that record.
Questions on the NCA ECC and external monitoring
Which NCA ECC controls does external exposure monitoring produce evidence for?
Six subdomains of ECC-2:2024 have a part that is visible from the internet: 2-1 Asset Management, 2-10 Vulnerabilities Management, 2-11 Penetration Testing, 2-13 Cybersecurity Incident and Threat Management, 2-15 Web Application Security and 4-1 Third-Party Cybersecurity. ShadowMap produces a dated record for that part of each.
Is Continuous Automated Red-Teaming the penetration testing in subdomain 2-11?
No. Subdomain 2-11 covers penetration testing of all externally provided services, conducted periodically, and a penetration test is an exercise carried out by people. Continuous Automated Red-Teaming validates external findings between those tests and states on each finding whether it was tested. Security Brigade, the company behind ShadowMap, carries out penetration tests as a separate engagement.
How does the NCA evaluate an entity against the ECC?
The Controls say the NCA evaluates compliance through multiple means, such as self-assessment by the entities, periodic reports of the compliance tool, and field auditing visits. A monitoring record does not take the place of any of them. It is the evidence an entity brings to them for its internet-facing estate.
Which version of the ECC does this page quote?
ECC-2:2024, the NCA’s update of ECC-1:2018, in the English PDF the NCA publishes, read on 18 November 2026. Check the NCA’s current text before relying on any quotation.
Other regimes: SAMA Cyber Security Framework, NIS2, NYDFS 500.
Put dates on the external half of your ECC evidence
In a 30-minute demo we open the six records in the table on a live estate. Or name one apex domain and a written exposure snapshot reaches you in two business days.