1. Home
  2. Case studies
  3. Platform security

Case study · Platform security

Security isn’t one feature. It’s built through the whole platform.

MFA matters, but it is only one layer. We secure platforms through access controls, permissions, application behaviour, logging, infrastructure, backups, patching and the way changes are managed after launch.

MFAExtra protection around access
RolesUsers only see what they should
DailyBackups on managed environments
OngoingSecurity continues after launch
Approach
Security by design
Access
MFA + role-based permissions
Infrastructure
Cloudflare, backups + patching
Management
Ongoing security after launch

The principle

Security has to work at every layer.

It is easy to point to one security feature and call a platform protected. Real security is broader than that.

On a platform like Rosewood, different people need very different access. Staff, students, parents and administrators cannot all see the same information, and especially sensitive areas such as safeguarding need stronger restrictions and clearer accountability.

That means security has to be designed into the login, the permissions, the application, the files, the infrastructure and the way the platform continues to be supported.

What needed protecting

  • Sensitive student and safeguarding information
  • Different user roles with very different levels of access
  • Files and documents uploaded through the platform
  • Messages and communication between users
  • Staff access to business-critical functions
  • The infrastructure and data sitting behind the application
Security should not sit around the edge of a platform. It should shape who can access it, what they can see and what happens when something changes.
Resolve Beyond platform security

How it is built

Five layers, not one security setting.

The strongest platforms are protected through several controls working together, so one weak point does not become the whole security model.

  1. 01 · Access

    Start with who is allowed in

    MFA adds another barrier around staff access, while secure login and session controls reduce the risk around accounts and active sessions.

  2. 02 · Permissions

    Being logged in does not mean seeing everything

    Role-based access and least-privilege permissions keep different areas of the platform restricted to the people who genuinely need them. Safeguarding information receives tighter controls than ordinary platform content.

  3. 03 · Application

    The platform itself has to handle sensitive activity safely

    File uploads, messaging, session handling, logging and security-sensitive actions all need controls at application level, including file-type restrictions, protected storage and audit trails where appropriate.

  4. 04 · Infrastructure

    The environment behind the platform needs protecting too

    Managed hosting adds another layer through Cloudflare, SSL, WAF protection, backups, server updates and infrastructure monitoring.

  5. 05 · Ongoing

    Security does not finish when the platform launches

    New vulnerabilities appear, users and permissions change, hosting evolves and the application keeps developing. Security patches and access changes have to keep moving with it.

5 layersaccess through to infrastructure
MFAstaff access protected
Dailybackups on managed environments
1 teamapplication and infrastructure together

The value comes from the layers working together. MFA is stronger when permissions are right, permissions are stronger when activity is logged, and the application is safer when the infrastructure underneath it is managed properly.

What was at stake

  • Sensitive student and safeguarding data
  • Users with very different access requirements
  • Files and messages moving through the platform
  • A live system continuing to change after launch
  • MFA and role-based access controls
  • Safeguarding information restricted and auditable
  • Secure file and application controls
  • Backups, Cloudflare and infrastructure protection
One password should never be the whole security strategy.

We build protection through the platform, the people using it and the infrastructure underneath it, then keep those controls moving as the system changes.

Talk to us about platform security

Inside the platform

Access should follow the job, not just the login.

On a complex portal, security is as much about what happens after login as the login itself.

Administrators, staff, students and parents need different permissions. Sensitive areas need stronger restrictions. Important activity needs to be traceable. Files need to be handled safely. That is why role-based access and application-level controls matter as much as MFA.

Sensitive information gets tighter controls

Safeguarding data is not treated like ordinary content. Access is restricted more tightly, with stronger logging and controls around who can view or change it.

Around the platform

Security continues outside the application too.

Cloudflare, backups, SSL, WAF rules, server security updates and infrastructure monitoring protect the environment the platform depends on.

Resolve Beyond also carries cyber insurance as part of our own operational protection. It does not replace technical controls on a client platform, but it reflects the fact that we treat access to client systems and infrastructure as a serious responsibility.

Ongoing security work can include

  • MFA and access reviews
  • Application security fixes
  • Server and infrastructure patching
  • Cloudflare and WAF configuration
  • Backups, monitoring and controlled releases
Explore ongoing support →

Questions

Platform security FAQs

Is MFA enough to secure a platform?

No. MFA is one important control, but platform security also depends on permissions, secure application behaviour, logging, infrastructure protection, backups, patching and ongoing maintenance.

Can different users have different levels of access?

Yes. Role-based access can be built around the people using the platform so administrators, staff, students, parents and other users only see the information and actions appropriate to them.

How do you protect the infrastructure behind a platform?

Infrastructure protection can include Cloudflare, SSL, WAF rules, backups, server security updates, monitoring and controlled production changes.

Does security stop once a platform is launched?

No. Security requires ongoing work as vulnerabilities are disclosed, users and permissions change, infrastructure evolves and the application itself continues to develop.

More questions? See our full FAQ →

Talk to us

How secure is the whole platform, not just the login?

We can review access, permissions, application controls, hosting and the ongoing processes around your platform to find where security needs strengthening.

Security issue right now? Bring us the problem →

Hartlepool, UK. Working with clients across the UK, US, Middle East and Asia.