> For the complete documentation index, see [llms.txt](https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/assessment-guide/core-assessment-sections.md).

# Core Assessment Sections

### **Overview**

The Digital Pillar Assessment is structured around five key architecture areas: Business, Data, Application, Technology, and Security. Each area plays a critical role in building a robust digital and cybersecurity framework, supporting organisations in achieving and progressing through maturity levels (Bronze, Silver, and Gold).

Each assessment section includes exemplar statements, questions, and scoring criteria that allow organisations to evaluate their current capabilities and set clear targets for improvement.

{% embed url="<https://app.guideflow.com/player/3r3qj9wtnk>" %}

***

### **1. Business Architecture**

The Business Architecture section assesses how well digital and cybersecurity practices align with organisational goals and regulatory compliance.

* **Focus Areas**:
  * **Strategy**: Ensuring digital initiatives align with compliance and operational goals.
  * **Processes**: Digitalising core business processes to meet compliance standards.
  * **People/Organisation Structure**: Defining roles and training employees in essential digital skills.
  * **Compliance**: Ensuring adherence to industry regulations (e.g., GDPR).
* **Key Outcomes**: A digital strategy that is integrated into the organisation’s business goals, supports compliance, and drives operational efficiency.

***

### **2. Data Architecture**

The Data Architecture section examines the management, security, and governance of data, which are essential for supporting secure and reliable operations.

* **Focus Areas**:
  * **Data Management**: Establishing secure storage and access controls.
  * **Data Security**: Implementing encryption and access controls to protect data.
  * **Data Governance**: Setting policies for data use, privacy, and protection.
  * **Data Quality**: Maintaining accurate and reliable data for informed decision-making.
* **Key Outcomes**: A secure, compliant, and well-governed data framework that supports organisational goals and ensures data integrity.

***

### **3. Application Architecture**

The Application Architecture section evaluates the security, usability, and integration of essential business applications.

* **Focus Areas**:
  * **Core Applications**: Securing applications that support core operations (e.g., ERP, CRM).
  * **Integration**: Enabling data flow and integration across systems.
  * **User Experience (UX)**: Designing applications for ease of use and productivity.
  * **Security**: Protecting applications through role-based access controls and regular updates.
* **Key Outcomes**: An application environment that is secure, user-friendly, and fully integrated, supporting productivity and digital resilience.

***

### **4. Technology (Infrastructure) Architecture**

The Technology Architecture section assesses the robustness and security of the organisation’s digital infrastructure.

* **Focus Areas**:
  * **Servers and Compute**: Ensuring infrastructure reliability and uptime.
  * **Networks**: Building secure, stable connectivity for daily operations.
  * **Cloud Services**: Using cloud solutions for flexibility and continuity.
  * **Reliability and Uptime**: Maintaining stable infrastructure for continuous operations.
* **Key Outcomes**: A reliable, secure infrastructure that provides the foundation for secure and efficient business operations.

***

### **5. Security Architecture**

The Security Architecture section focuses on protecting organisational assets through comprehensive cybersecurity controls and incident response plans.

* **Focus Areas**:
  * **Cybersecurity Controls**: Implementing essential security measures (e.g., firewalls, antivirus).
  * **Data Protection**: Regularly backing up and encrypting sensitive data.
  * **Incident Response**: Preparing response plans to handle cyber threats.
  * **Compliance**: Aligning security policies with regulatory requirements (e.g., ISO, GDPR).
* **Key Outcomes**: A resilient cybersecurity framework that safeguards data and processes from threats, supporting both regulatory compliance and operational security.

***

### **Moving Forward with the Core Assessment Sections**

Each core section is crucial to achieving digital maturity and cybersecurity resilience. By addressing these architecture areas, organisations can build a comprehensive digital strategy that aligns with both operational and security goals. For detailed guidance on completing the assessment, proceed to the [**Digital Pillar Assessment Tool**](/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/assessment-guide/preparing-for-the-assessment.md) page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/digital-and-cybersecurity-pillar/assessment-guide/core-assessment-sections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
