Architecture and Solution Design

A written target for how the pieces should work together, before anyone buys or builds.

Already have an IT provider? Here's how we work together.

A county agency choosing a new case system

The system chosen before the questions

The challenge. A county office is about to replace its case-management software. Three vendors have demonstrated their products. Staff like the second one, the budget fits the third, and nobody has asked where the data will live, who will sign in and how it connects to the state’s systems.

The insight. Security is cheapest at the design stage. A short design that states the data, the people, the connections and the rules lets every vendor answer the same questions, and turns a comparison of demonstrations into a comparison of fit.

The decision. The office paused the choice for three weeks to write the requirements first and ask each vendor to answer against them.

The action. We mapped the data and who touches it, drew how the system would connect to others, and wrote the security and privacy requirements in plain language: sign-in, roles, logging, encryption, backup, data location, exit terms. We scored each vendor’s written answers and listed the open questions for a second round. The vendor and the IT provider handled the build; we reviewed the design before go-live.

The result. The office chose a vendor on written answers, signed a contract that carries the requirements, and has a design diagram it can hand to the next person.

What Security Medic does

Security architecture

How networks, identity, data and devices fit together, shown as a simple diagram and a short list of rules.

Solution design and vendor requirements

The security and privacy requirements for a new system, ready to put into a request for proposal or a contract.

Design reviews

A review of a vendor’s or an IT provider’s design before build and again before go-live.

Design for AI and privacy

Where AI tools may be used, what data they may see and how personal information is limited from the start.

Where this sits in the cycle

Every client goes through the same six steps, from a town office to a family at home. The Security Medic method

  1. 1. Govern
  2. 2. Design
  3. 3. Assess
  4. 4. Review
  5. 5. Conform
  6. 6. Improve
  • Govern. The goals, the data that matters most and the risk the organization accepts.
  • Design. The target architecture and the requirements that follow from it.
  • Review. Vendor answers and designs judged against the requirements.
  • Conform. Builders build; we check the result against the design before go-live.
  • Improve. The design is updated as the system and the rules change.

The standards we draw on

The NIST Cybersecurity Framework 2.0 for structure, NIST SP 800-53 and NIST SP 800-160 for engineering detail, the NIST Privacy Framework and the NIST AI Risk Management Framework where personal data or AI is involved, and the sector rules that apply, such as HIPAA, CJIS or New York Education Law § 2-d.

Threat modelling →Security testing →Working with your IT provider →

Getting ahead of it

Write the requirements before the next purchase, and the same document serves the next three.

Start with a free 30-minute call

Tell us what you are about to buy or build. We will talk through the questions worth asking first.

Book a free 30-minute call