CORE // ACTIVE

CONFIDENTIAL // AUTHORIZED RECIPIENTS ONLY

REF: THRT-UNK-7729

Security plan

The security steps your business needs to take, in the order that matters most for you.

At risk or partial

8

Needs evidence

19

Verified

0

Needs evidence means we do not have current evidence for a capability yet. It is not a failed configuration. Built from 4 connected tools: Cloudflare, GitHub, Google Workspace, Vercel.

?

Architecture context

5 open questions affect where protections apply.

Review in Architecture
Search program items...
Filter
Group:Horizon
Sort:Priority
Plan
By area
Scenarios
Quick wins
27 of 27

Focus now

8 Next 30 days
At risk
Start here

Secure administrator access

Identity and access

Protect the accounts that can change security settings, billing, and production access.

Why this matters for your business

Administrator accounts can change anything: add people, remove protections, and hand out access to your code and customer data. If one is taken over, nothing else has to be broken.

Why we can say that
Members can sign in with just a password, so a stolen password alone would be enough for someone to get into your organisation. Requiring a second form of verification would close this gap.
3 requirements have no evidence yet
See all 4 requirements and 1 finding
Review finding
Discuss
At risk

Secure workforce sign-in

Identity and access

Ensure people need a strong second factor when they access company systems.

Why this matters for your business

Most break-ins at companies your size start with one reused password. A second step at sign-in is the cheapest answer to that, and it is the first thing a customer security questionnaire asks about.

Why we can say that
Members can sign in with just a password, so a stolen password alone would be enough for someone to get into your organisation. Requiring a second form of verification would close this gap.
6 requirements have no evidence yet
See all 8 requirements and 1 finding
Review findings
Discuss
At risk

Manage privileged access

Identity and access

Limit powerful access, keep it separate from everyday work, and restrict delegated roles.

Why this matters for your business

Powerful access used for everyday work turns a routine mistake into a company-wide one. Keeping it separate, and handing it out only when it is needed, is what keeps a bad day small.

Why we can say that
Any member of your organisation can invite outside people to join, without an administrator needing to approve it first.
4 requirements have no evidence yet
Requirements
Outstanding invitations do not retain broad or privileged access At risk

A direct violation is currently open.

GitHub An unaccepted invitation allows code changes Review finding
GitHub An unaccepted invitation grants more than ordinary access Review finding
GitHub An unaccepted invitation carries access to every repository Review finding
GitHub Any member can invite people from outside the organisation Review finding
VercelCloudflare 2 tools are connected, but have not been assessed yet. Run assessment
AWS AWS is part of your security plan, but it is not connected yet. Connect integration
Administrator privileges are limited to the people who need them Needs evidence

A connected service still needs a verifiable evidence path.

GitHub Too many people have full control of the organisation Review finding
GitHub Too many people have full control of this repository Review finding
AWS AWS is part of your security plan, but it is not connected yet. Connect integration
VercelCloudflare+1 3 tools are connected, but have not been assessed yet. Run assessment
Privileged access is not exposed through everyday or suspended accounts Needs evidence

A connected service still needs a verifiable evidence path.

CloudflareGoogle Workspace+2 4 tools are connected, but have not been assessed yet. Run assessment
AWS AWS is part of your security plan, but it is not connected yet. Connect integration
Delegated administrative roles are restricted to their intended scope Needs evidence

A connected service still needs a verifiable evidence path.

GitHub Someone outside the organisation can change code Review finding
Google WorkspaceVercel+1 3 tools are connected, but have not been assessed yet. Run assessment
AWS AWS is part of your security plan, but it is not connected yet. Connect integration
Critical service access is provisioned through the company directory Needs evidence

A connected service still needs a verifiable evidence path.

VercelCloudflare 2 tools are connected, but have not been assessed yet. Run assessment
AWS AWS is part of your security plan, but it is not connected yet. Connect integration
Review findings
Discuss
At risk

Protect secrets in delivery systems

Software delivery

Keep deployment credentials out of public builds and limit which code and environments can access them.

At risk

Protect production changes

Software delivery

Ensure production code and deployments receive the right review and protection.

At risk

Secure build automation

Software delivery

Constrain workflow authority, require approval for untrusted changes, and isolate build machines.