Hey,
Last week was about your first 90 days in the job. This week is for the person who's still choosing, and who has heard "GRC" a hundred times without anyone explaining it in plain English.
If you've ever asked, "Is there a cybersecurity job where I don't have to code?", GRC is one of the answers. It isn't the only one, and it isn't "no technology". But it's a path that plenty of career changers overlook.
π₯ This Week's Insight: GRC Is Making Sure a Company Does What It Says It Does
GRC stands for governance, risk and compliance. Forget the three words for a moment. Here's the plain version:
GRC is making sure an organisation does what it says it does about risk and rules.
A company tells its customers, its regulators and its auditors that it looks after their data and follows certain rules. GRC people are the ones who make sure that's actually true, and who can prove it.
In practice, it comes down to four activities.
Activity In plain English What it looks like at work 1. Write the rules Decide what "good" looks like, and put it in writing Policies, standards and short procedures. For example: "Every laptop must be encrypted." 2. Find what could go wrong Spot the risks and rate them A risk register: a list of what could go wrong, how likely it is, how bad it would be, and who owns it 3. Prove it's being done Check the rules are followed, and keep the evidence Control tests, evidence folders, helping auditors 4. Explain it to people Turn it into something others can act on Reports for managers, answers to auditors and customers, short training
You'll hear names like ISO 27001, SOC 2 and GDPR. ISO 27001 and SOC 2 are sets of expectations that a company can be checked against. GDPR is a law. Don't try to memorise any of them yet. They're simply where "the rules" often come from.
You may already do versions of all four
Many career changers do these things in their current job without calling them GRC:
Writing the rules: if you've written a how-to guide, a checklist or a process for a team.
Finding what could go wrong: if you've worked on a project plan with a risk list, done a safety or quality check, or spotted errors or fraud in finance.
Proving it's done: if you've kept records for an audit, signed something off, or checked expenses against a policy.
Explaining it: if you've turned something complicated into something a busy person can act on, in teaching, support or account management.
You won't have all four, and that's fine. It does mean you're starting from more than zero.
What GRC is not
An honest word, so you can decide with open eyes:
It isn't "no technology." In many GRC roles you don't write code. But you do need to understand how systems work well enough to ask sensible questions, like "Does this need a second login step, and why?"
It isn't only paperwork. The hard part is judgement: deciding what matters most, and saying so clearly.
It may not suit you if you want to spend your day on alerts and logs. That's the SOC path, and it's a different kind of work.
No guarantees. Routes into GRC vary a lot, and I can't promise how quickly one will open up for you.
π οΈ Free Tool of the Week: The Path Assessment
Not sure whether GRC fits you? Answer a few questions about your background and how you like to work, and it matches you to one path.
Free, with no signup to see your results
Covers SOC, GRC, IAM, Cloud and Pentest
Treat the result as a starting point, not a verdict
If GRC comes up, the action below is for you. If it doesn't, nothing here is wasted, because thinking in risks helps on every path.
π‘ Career Advice From the Hiring Table: Build One Small Thing to Prove It
A certificate shows you can answer questions. A piece of real work shows you can do the job. For GRC, the simplest piece of real work is this:
Build a risk register for a fictional company, and write it up on GitHub.
Make up a small company, such as an online print shop or a small clinic's booking system. Decide what it can't run without, find what could go wrong, rate each risk, and say what you'd do about it.
What to put in the write-up
The company. Who they are, what they sell, and which data and systems matter most.
Your method. How you rate each risk. Keep it simple: likelihood from 1 to 5, impact from 1 to 5, and rating = likelihood Γ impact. Say what counts as Low, Medium and High.
The register. 10 to 15 risks in a table.
Your top three. Why each one matters in business terms, and what you'd recommend.
Your reflection. What the project taught you, and what you'd improve with more time.
A starter table for the register (the example and its numbers are made up):
ID Risk statement Likelihood Impact Rating Treatment Owner Review date R1 The customer order database could be accessed by an outsider because all staff share one admin password, exposing customers' names and addresses and leading to complaints and lost trust. 3 5 15 (High) Reduce: individual accounts and a second login step Operations manager Quarterly
What makes a write-up worth reading
Say why you did it. "My goal was to learn" is true, but it isn't enough. Your goal is to complete a real work-like task, so an employer can see you can do it, and there's proof.
Show what it taught you, and how you'd improve it. Self-reflection stands out.
Quantify, don't just list. "12 risks: 3 High, 6 Medium, 3 Low, and the three I'd fix first" beats a bare list.
Connect it to the business. Say which real problem it would solve for a company.
Be honest that it's fictional. Don't invent results. Your numbers come from your own method, so explain it.
π― Your One Action This Week
Write five risk statements for a company you know. Use this form:
Asset + threat + vulnerability + impact
Or as a sentence: "[Asset] could be [threat] because [vulnerability], leading to [impact]."
Pick a company you know. A shop you use, a club you belong to, or a small business. If you pick an employer, use only what anyone could see from the outside. Never use confidential details.
List five things it can't run without. Those are your assets.
For each one, name one thing that could go wrong (the threat) and one weakness that makes it possible (the vulnerability).
Write the sentence.
Read it back. Would a non-technical manager understand the impact? If not, rewrite it.
Here's the difference between weak and better:
Weak Better "Hackers could steal our data." "The shared booking spreadsheet could be seen by someone who shouldn't have it, because everyone in the team has edit access, including temporary staff, leading to customers' phone numbers being shared and complaints." "Phishing is a risk." "Staff email accounts could be taken over through phishing, because the company doesn't require a second login step, letting an attacker send fake invoices to customers."
All you need is half an hour or a bit more. Then hit reply and send me your best one, with no company secrets. I read every one.
π§° Free Tools, If You Haven't Tried Them Yet
π§ Not sure which path? path.mpcybersecurity.co.uk matches your background and working style to one path.
π Not sure what to study next? skills.mpcybersecurity.co.uk shows what's missing for your target role.
π§ Preparing for Security+? practice.mpcybersecurity.co.uk gives you an explanation on every answer.
π Ready to apply, but hearing nothing? cv.mpcybersecurity.co.uk shows what the software sees first.
All free. No signup required to see your results.
π A Look Behind the Curtain: What's Inside the Community
Everything in this issue is free, and you can do all of it on your own. Plenty of people do. If you'd like someone to check your work, here's a small look at what members get.
A full GRC project in the study plan
The six-week GRC plan runs at about 3-4 hours a week, with weekly checklists, and ends with a full GRC project you can put on your GitHub. There are plans for SOC, IAM, Cloud and Pentest too.
A real work ticket, every week
For GRC, that might be a control test or a vendor review, scored on accuracy, reasoning and communication. Members review each other's work, then compare against my model answer.
A scenario question, every weekday
Here's a recent GRC one:
"Your retention policy says delete customer records after seven years. Legal has just told you there's an active dispute involving some of them, and the deletion job runs on Friday night. What do you do, and who needs to agree?"
Members post their answer and their reasoning, and I read and reply.
And the rest
A live Q&A with me every Wednesday at 8pm GMT. Study groups by path. CV, LinkedIn and GitHub templates. And CV and portfolio reviews from someone who hires for these roles.
No guarantees, and I can't promise you a job. The more you get involved, the more you get out of it. It's $39 a month, and you can cancel any time.
π Join here
Hit reply and tell me which of the four activities you already do at work. I read every one, and it helps me decide what to cover next.
See you next week.
Marius Poskus Global VP of Cybersecurity / CISO CTRL+ALT+DEFEND
Skool Community | YouTube | LinkedIn
You're receiving this because you downloaded a resource from CTRL+ALT+DEFEND or subscribed to the newsletter. Next week: Issue #16, AI Study Tools: Learn Faster Without Fooling Yourself.