BBM-STD-87-SECURITY_MANAGEMENT-V0.1 | Office standard | 4 November 2026 | V0.1 | Private controlled WIP draft for office review
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-11-04 | First issue: closes rows (security part),, (security part),, (security part),, (CDE provider part),, (SensitivityClass) (ISO 19650-5 content; §1.3 row "Security-minded approach per ISO 19650-5") + cross-doc pointer pass: BBM-STD-51 §3 register IDs cited (ED-ISO19650-5, ED-ISO27001, ED-UAE-PDPL, ED-SIRA) |
1 Purpose ownership and scope#
This standard applies ISO 19650-5:2020 (edition 1, confirmed 2025) to office projects (edition record: register row ED-ISO19650-5 in BBM-STD-51 §3): a sensitivity assessment and security triage at the start, a security management plan where the triage requires one, security information and breach management, and information sharing agreements with every party that receives sensitive information. It owns the security triage form and the security management plan (SMP). The Manual §9.4 and Annex W2 S1–S3 keep the procedure summary and the synthetic security forms; their SEC record, access and incident fields are the fields used here. Personal data obligations (UAE PDPL, register row ED-UAE-PDPL) are owned by BBM-STD-90; retention and disposal schedules also live there.
| Role | Duty |
|---|---|
| Office Security Lead | Owns this standard; runs the triage with the project IT/data owner; approves the SMP; first contact for incidents |
| Lead appointed party (LAP) / information manager | Applies the SMP in the BEP, CDE permissions and exchange records; records the SensitivityClass of every container |
| Appointing party (client) / asset owner | States security requirements in the EIR and decides on asset-level sensitivity it alone knows |
| Task team leads | Apply the controls to their team's containers; report incidents at once |
| Legal / contract owner | Decides notification duties and agreement terms; this standard gives no legal advice |
Role holders are named in the restricted Directory; responsibilities matrix in BBM-STD-55.
2 Sensitivity assessment and security triage#
Run the triage at appointment, before the CDE is opened to any party, and again at each trigger in §6. ISO 19650-5 clause 4 is the reading pointer; check the licensed text before claiming conformity.
| Triage form field | Content |
|---|---|
| Triage ID / revision | SEC-TRI-<PROJ>-Rnn, date, assessor, reviewer |
| Asset and site | Asset type and use, location sensitivity, owner/occupier profile (no personal names in the form) |
| Information in scope | Datasets and containers (models, drawings, coordinates, security and life-safety systems, building services control, occupancy data), with aggregation risk (individually harmless items that are harmful together) |
| Harm questions | Could disclosure, aggregation, wrong change or loss of this information help someone harm the asset, its occupants or its services, or cause commercial or personal-data harm? Confidentiality / integrity / availability consequence per dataset |
| Client and authority requirements | EIR security clauses; authority rules (e.g. security-system drawings under the current SIRA / DM requirement for the plot, confirmed at permit stage: BBM-STD-85 §8) |
| Outcome | Triage outcome (below), rationale, reviewer decision and date |
| Next review | Trigger or date |
| Triage outcome | Meaning | Required action |
|---|---|---|
| T0 Not sensitive | No credible harm from disclosure or aggregation | Office baseline controls (§4); record the justification, never assume |
| T1 Sensitive | Security-minded approach needed for part or all of the information | SMP (§3), SensitivityClass on every affected container, information sharing agreements (§5) |
| T2 Sensitive, externally directed | The client, asset owner or an authority sets the security regime (e.g. security systems, critical services) | SMP that adopts the external regime as written; the external party's rules prevail where stricter |
The three-outcome scale is an office decision; ISO 19650-5 requires the assessment and a proportionate response, not these labels. The assessment detail itself is restricted to the Security Lead, the reviewer and the appointing party.
SensitivityClass. Every container in the CDE, and every delivery row in the MIDP / TIDP, carries SensitivityClass: Public, Internal, Confidential or Restricted (security-system and other T2 information is at least Confidential). The class decides the CDE area, recipients and transfer route.
3 Security management plan#
Required for T1 and T2. ISO 19650-5 clauses 5–9 are the reading pointers. The SMP is an annex of the BEP (§1.13 and §10.4 carry only the pointer and the SensitivityClass list).
| SMP section | Content |
|---|---|
| S1 Scope and outcome | Triage ID and outcome, datasets covered, client and authority requirements adopted |
| S2 Roles | Security Lead, IT/data owner, LAP contact, appointing-party security contact |
| S3 Classification and labelling | SensitivityClass per dataset; label in container metadata and title block; derivative (redacted) versions and who approves them |
| S4 Access | Least-privilege CDE roles per class; MFA on CDE accounts; privileged memberships reviewed monthly with evidence; joiner / mover / leaver steps linked to the Directory |
| S5 Transfer and storage | Approved CDE and transfer routes per class; no sensitive input to unapproved plug-ins, AI services or public validators (BBM-STD-92); hosting region of the CDE recorded |
| S6 Suppliers | Each receiving party signs the information sharing agreement (§5); CDE provider evidence: ISO/IEC 27001 certificate scope and expiry, hosting region |
| S7 Breach management | §4 procedure, contacts, evidence custody |
| S8 Retention and disposal | Pointer to the schedule in BBM-STD-90; legal hold blocks disposal |
| S9 Review | Triggers in §6; awareness briefing recorded for each team member before access |
4 Security information and breach management#
Baseline controls (all projects). Named CDE accounts only; no shared logins; permissions by role, not by person; downloads of Confidential and Restricted containers logged; backups follow BBM-STD-76.
Breach or incident procedure.
| Step | Action | Record |
|---|---|---|
| B1 Report | Anyone who sees a suspected disclosure, loss or wrong change reports to the Security Lead at once through the approved channel | IncidentID, discovery time with UTC offset, reporter role |
| B2 Contain | Security Lead with IT suspends the affected access or share link; preserve logs and evidence; do not delete or broadcast screenshots | Containment action, authoriser, time |
| B3 Assess | Affected datasets, revisions, hashes and recipients; consequence against the triage | Assessment, reviewer |
| B4 Notify | Legal/security owner decides who is notified (client, authority, affected people under PDPL via BBM-STD-90) and when | Decision, approver, transmission evidence, or reasoned decision not to notify |
| B5 Recover | Restore only a verified baseline; re-test allowed and denied routes before re-opening | Baseline ID, test results |
| B6 Close | Corrective action, SMP update, lessons briefed | Closure date, SMP revision |
The detailed incident record fields are those of Manual Annex W2 S3.
5 Information sharing agreement#
Every party that receives T1/T2 information signs an information sharing agreement before access. The contract owner records the agreed instrument and revision; the schedule below is the minimum content, not contract wording.
| Clause topic | Minimum content |
|---|---|
| Parties and purpose | Receiving organisation and role, permitted purpose, datasets and SensitivityClass |
| People | Named-role access only; awareness briefing before access; leavers removed within the agreed time |
| Handling | Approved storage and tools; no onward sharing, sub-processors or AI services without written approval; local copies controlled |
| Incidents | Report to the Security Lead at once; cooperate in containment and evidence |
| End of use | Return or deletion of copies with written confirmation; backup treatment stated |
| Review | Agreement reviewed at each trigger in §6 |
6 Review triggers and ISO/IEC 27001 link#
Repeat the triage and update the SMP at: new recipient or supplier; change of dataset, aggregation or asset use; change of CDE, tool or host; any incident; each stage gate; handover to operation.
Where the office or the CDE provider holds or adopts an information security management system, the controls map to ISO/IEC 27001:2022 + Amd 1:2024 Annex A (register row ED-ISO27001). Control IDs below are as titled in the 2022 edition; confirm against the licensed text before claiming conformity.
| This standard | ISO/IEC 27001:2022 Annex A control |
|---|---|
| SensitivityClass, labelling (§2, S3) | 5.12 Classification of information; 5.13 Labelling of information |
| Transfer routes (S5), sharing agreement (§5) | 5.14 Information transfer; 6.6 Confidentiality or non-disclosure agreements |
| Access, MFA, privileged review (S4) | 5.15 Access control; 5.16 Identity management; 5.17 Authentication information; 5.18 Access rights; 8.2 Privileged access rights |
| Suppliers, CDE provider (S6) | 5.19–5.22 Supplier relationships; 5.23 Information security for use of cloud services |
| Breach procedure (§4) | 5.24–5.28 Information security incident management |
| Awareness (S9) | 6.3 Information security awareness, education and training |
| Personal data (BBM-STD-90) | 5.34 Privacy and protection of PII |
| Backup, deletion, media (BBM-STD-76, S8) | 8.13 Information backup; 8.10 Information deletion; 7.10 Storage media |
References#
- ISO 19650-5:2020, edition 1, confirmed 2025: https://committee.iso.org/standard/74206.html, checked 2026-11-04. Clause 4 sensitivity assessment; clauses 5–9 security-minded arrangements (reading pointers).
- ISO/IEC 27001:2022 + Amd 1:2024: https://committee.iso.org/standard/82875.html, checked 2026-11-04.
- UAE PDPL, Federal Decree-Law No. 45 of 2021, effective 2 Jan 2022, Active: https://uaelegislation.gov.ae/en/legislations/1972, checked 2026-11-04 (obligations owned by BBM-STD-90).
- SIRA rule: no SIRA or DM primary source confirmable on 2026-11-04; dependence-free rule in BBM-STD-85 §8.
- IMI Framework (formerly UK BIM Framework, renamed May 2025), resources incl. security guidance: https://ukbimframework.org/resources/, checked 2026-11-04.
- Office: Manual §9.4 and Annex W2 S1–S3, BBM-STD-55, BBM-STD-76, BBM-STD-85, BBM-STD-90, BBM-STD-92; proposed decision.