Data architecture

Data architecture is all about how you collect, store, manage, transform and use data. We consider how the data is gathered from various sources as well as the data residency, or where the physical servers holding the data are located. For a lot of our clients, it needs to be stored in the UK.

We meet data standards for encryption every time we move or store data. In line with GDPR regulations, we have audit trails of when data has been changed, who made that change and when it was made. That means if there’s ever an issue, we can refer back to audit information.

Data has to be accessible to only the right people at the right time. This is called the principle of least privilege, where you only have access to the data you absolutely need and no more. Even CEOs have data restricted from them if it’s not relevant to their role.

Together the team defines:

• How the data is collected?

• Is a data migration required?

• What format does the data need to be in?

• Does the data need transforming?

• How will data be handled in each service?

• How will the data be distributed and shared?

• How will the data be consumed and secured?

• What permissions need to be allocated?

• What audit logs will there be for that data?

Using the principles and criteria listed above, the data team can design and implement secure data architecture.