Arcfield 4 · Context audit
Source: Arcfield EN Companion · Volume 1 audit + OSCAL assessment plan (AP) / assessment results (AR) · oscal/assessment-plan.md, oscal/assessment-results.md · HITL: oscal-guide.md · SIMULATION
How this report is elaborated
Scope is the Volume 1 4 · Context audit. Identities are the applicable ISO clauses or Annex A controls in this prefix. Process topics remain the operational evidence (foundation, implementation).
The process we followed is ISO 27001 → Policies → Processes and Systems → Protected Assets → Objects needed by the process → Evidences. Standard vs policy examines whether a policy covers the cited clause or control. Policy vs evidence tests the join from policy rule to recorded evidence.
How to read this report
Start with Results at a glance, then how this category is set up. Glance is Conformity (share without an NC) plus Defined / Implemented / Effectiveness. An NC is recorded when there is no policy and no implementation evidence (Requirement ↔ evidence), when a measure is implemented without effectiveness evidence (Requirement ↔ evidence), or when the kernel join FAILs (Policy ↔ evidence, default minor). Standard vs policy stays HITL. Presence is not Defined = yes as a coverage PASS. UNKNOWN is not an NC.
Results at a glance
Conformity is the share of applicable identities without an NC. Companion Contract/Example unchanged. This is not a certification statement.
How 4 · Context is set up
Upper row is documented information. Lower row is operating evidence. Green is installed here. Dashed is named, not packed. The subject is the clause or control.
Documented evidence in this pack. Not a certification PASS.
Documented evidence in this pack. Not a certification PASS.
Documented evidence in this pack. Not a certification PASS.
Documented evidence in this pack. Not a certification PASS.
Documented evidence in this pack. Not a certification PASS.
Named implemented evidence. Not in this pack.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Implemented evidence in this pack. Not a certification PASS.
Topic reports remain the process evidence: foundation, implementation.
Nonconformities
Nonconformities this pack can show. Kernel FAIL is Policy ↔ evidence, default minor — not an automatic major. No policy and no implementation, or implementation without effectiveness evidence, is Requirement ↔ evidence. UNKNOWN is not an NC. Assessment Results stay the kernel SSOT. How to fix is the follow-up, not a customer ticket.
| Requirement | Statement | Grade | Path | Detail |
|---|---|---|---|---|
| 4.1 Understanding the organization and its context | 4.1 Understanding the organization and its context has no policy and no implementation evidence in this pack. | minor | Requirement ↔ evidence | NC-C4-not-implemented |
| 4.2 Understanding the needs and expectations of interested parties | 4.2 Understanding the needs and expectations of interested parties has no policy and no implementation evidence in this pack. | minor | Requirement ↔ evidence | NC-C4-not-implemented |
| 4.3 Determining the scope of the ISMS | 4.3 Determining the scope of the ISMS has no policy and no implementation evidence in this pack. | minor | Requirement ↔ evidence | NC-C4-not-implemented |
| 4.4 Information security management system | 4.4 Information security management system is named in this pack, but there is no effectiveness evidence. Cited implementation: WIR-S1, IMPL-WB. | minor | Requirement ↔ evidence | NC-C4-missing-evidence |
ISO 27001 norms and controls
Cited clauses and Annex A controls for this category. Defined is a cited policy (HOW). Standard vs policy stays HITL: Defined = yes does not score that the text covers the control. Implemented is in-pack or named operating evidence. Effective is the kernel join or HITL effectiveness. No policy and no implementation is an NC. Implementation without effectiveness evidence is an NC. Ratings are yes, no, or partially. DK or NA when this pack has no data.
| Index | Name | Kind | Defined | Implemented | Effective |
|---|---|---|---|---|---|
| 4.1 | Understanding the organization and its context | clause | no | no | DK |
| 4.2 | Understanding the needs and expectations of interested parties | clause | no | no | DK |
| 4.3 | Determining the scope of the ISMS | clause | no | no | DK |
| 4.4 | Information security management system | clause | no | yes | no |
What we found
What this pack actually cited for this clause or control identity. Counts are from this pack. Presence is not a PASS. No ISO shall-text.
4.1 Understanding the organization and its context
Quantitative
- Defined / Implemented / Effective = yes: 0/3 (DK/NA not counted as yes).
- Nonconformities (major/minor) on this identity: 1.
- Cited artefact IDs: 0.
Qualitative
This pack cites no companion artefacts on this identity. Nonconformities recorded: 4.1 Understanding the organization and its context has no policy and no implementation evidence in this pack.. Other-book files stay on acquire pages. This chapter does not invent their content.
4.2 Understanding the needs and expectations of interested parties
Quantitative
- Defined / Implemented / Effective = yes: 0/3 (DK/NA not counted as yes).
- Nonconformities (major/minor) on this identity: 1.
- Cited artefact IDs: 0.
Qualitative
This pack cites no companion artefacts on this identity. Nonconformities recorded: 4.2 Understanding the needs and expectations of interested parties has no policy and no implementation evidence in this pack.. Other-book files stay on acquire pages. This chapter does not invent their content.
4.3 Determining the scope of the ISMS
Quantitative
- Defined / Implemented / Effective = yes: 0/3 (DK/NA not counted as yes).
- Nonconformities (major/minor) on this identity: 1.
- Cited artefact IDs: 0.
Qualitative
This pack cites no companion artefacts on this identity. Nonconformities recorded: 4.3 Determining the scope of the ISMS has no policy and no implementation evidence in this pack.. Other-book files stay on acquire pages. This chapter does not invent their content.
4.4 Information security management system
Quantitative
- Defined / Implemented / Effective = yes: 1/3 (DK/NA not counted as yes).
- Nonconformities (major/minor) on this identity: 1.
- Cited artefact IDs: 2.
Qualitative
Cited artefacts in this pack: WIR-S1, IMPL-WB. Nonconformities recorded: 4.4 Information security management system is named in this pack, but there is no effectiveness evidence. Cited implementation: WIR-S1, IMPL-WB.. Other-book files stay on acquire pages. This chapter does not invent their content.