Security architecture and design
SECURE BY DESIGN
Littlefish Group applies a Secure by Design approach across every digital solutions engagement we deliver, embedding security into the architecture of every cloud migration, Microsoft 365 deployment, Dynamics 365 ERP implementation and Power Platform solution from the point of scoping through to handover.
Our Secure by Design approach
-
Threat modelling before architecture decisions are made
Before we finalise any architecture, we analyse the threat landscape specific to your sector, your environment and the solution being built. NHS trusts, financial services firms, utilities and central government organisations each carry distinct compliance obligations and threat profiles, including DSPT, FCA operational resilience requirements and NIS Regulations, and we account for these in our design decisions before they are locked in.
-
Least privilege access configured correctly from the start
We scope every user account, service principal and application integration to the minimum permissions its function requires, configuring this before any settings are written rather than correcting it once a solution is in use. We apply Microsoft Entra ID conditional access policies and role-based access control as standard, with Privileged Identity Management (PIM) implemented where standing administrative access carries unacceptable risk.
-
Data governance built into every solution
We treat data classification, GDPR obligations and retention requirements as design inputs rather than post-deployment findings, which means they shape the solution itself rather than being layered over it once it is live. For organisations in the Microsoft ecosystem, we implement Microsoft Purview as part of the deployment, covering information protection labels, data loss prevention policies and retention configurations from go-live.
-
Security control validation before every handover
Before any solution moves into live operation, we validate security controls against the original design intent, covering access configuration, data governance settings, network controls, audit and logging coverage and integration boundaries. This confirms that what we designed is what we built, that configurations have not drifted during delivery and that your team inherits a known, tested environment from go-live.