L1Baseline
The baseline customers and regulators keep asking for
What customers and regulators ask for first
- Time to reach it
- Within 3 months of onboarding
You are likely here if
- Your first big customer just sent a security questionnaire
- Nobody owns security yet, or it is a side job
- Policies live in scattered docs, or nowhere
What we put in place
- A named security owner, a risk list and short, approved policies
- Two-step sign-in, same-day leaver removal, admin reviews
- Device encryption, updates and remote wipe
- Backups with tested restores and an incident plan
- Evidence collected per control on a schedule
L1 covers 10 areas, each checked against evidence from your own systems
- 01Access and identityOnly the right people get in, and only for as long as they should.Two-step sign-in on email, code, cloud and admin tools · Leavers lose access the same day · Admin access reviewed on a schedule
- 02AwarenessPeople know what to watch for and how to raise a flag.Training at joining and every year · One-step reporting of suspicious messages · A second check before payment details change
- 03DevicesEvery laptop and phone that touches work is known and protected.A list of devices and who has them · Encryption, screen lock and updates enforced · Remote lock or wipe when one is lost
- 04Data and privacyYou know where personal data lives and how it is handled.A map of the data you hold · Encryption at rest and in transit · Steps for access, deletion and breach notification
- 05SuppliersThe companies you depend on are listed, owned and checked.A supplier list with an owner for each · A security check and a data agreement for critical suppliers
- 06Incidents and recoveryWhen something goes wrong, you know who acts and how you recover.Scheduled backups with a recorded restore test · An incident plan with contacts · Alerts that reach a named person
- 07Change and releasesWhat you ship is reviewed and scanned before it reaches customers.A second person reviews code · Secret and dependency scanning · A penetration test
- 08EvidenceEvery control has proof from your own systems, on a schedule.Evidence collected for each control · A written scope of what is covered
- 09AI governanceAI tools are in use on purpose, with clear limits.A list of the AI tools in use · A rule on what data may go into them
- 10Ownership and riskSomeone owns security, and the risks are written down.A named security owner · A risk list and a system list · Short, dated, approved policies
You end withA live L1 attestation shared through your trust portal