Governance, Risk, and ComplianceGovernance, Risk, and ComplianceGovernance, Risk, and Compliance

Examples of everyday tasks

• Identify and rate risks together with the people who run the systems.
• Match requirements from frameworks or regulations to specific controls.
• Collect and review evidence that controls are working.
• Track fixes with the responsible teams until they are done.
• Write policies and explain them in plain language.

Related job titles

• GRC analyst
• IT risk analyst
• IT auditor

These are career areas to explore, not a checklist. Some of these job titles usually require experience, and completing a starter project does not by itself make someone ready for them.

Starter project

Assess a Fictional Student Organization

Describe a fictional organization and its member platform. Identify a manageable set of risks and explain their relative importance.

This is a simulated assessment. Label it clearly as simulated wherever you share it.

What you’ll use

• A one-page description of a fictional organization that you write
• A risk register spreadsheet
• A framework to refer to, such as the NIST Cybersecurity Framework

Resources to start with

• NIST Cybersecurity Framework (opens in a new tab)

  A widely used framework for organizing and discussing security risks and controls.

More projects for this path

Each one comes with the framework to follow, five name ideas and a walkthrough for publishing it on GitHub.

• Student Org Risk Register

  Assess a fictional organization's platform and rank the risks with reasoning.

• Control Evidence Pack

  Pick five controls and collect the evidence that would satisfy an auditor.

Project walkthrough

1. Describe the fictional organization: who its members are, what information its platform stores, and who runs it.
2. List five to eight risks, such as officers sharing one password or member records having no backup.
3. Rate each risk’s likelihood and impact on a simple scale, and explain each rating in a sentence.
4. Rank the risks and explain why the top ones matter most.
5. Propose a control for each risk and name the role responsible for it.
6. For each control, describe the evidence that would show whether it works.

What to publish

• A risk register with likelihood, impact, and the reasoning for each rating
• Proposed controls and the roles responsible for them
• The evidence that would show whether each control works
• A clear label that this is a simulated assessment of a fictional organization

Optional extension

Reassess the risks after the proposed controls and explain the remaining uncertainty.

Example résumé bullet

Numbers are what make a bullet worth reading, so count them while you work: how much data you searched, how many findings you fixed, how many tests you added. Every figure should be one a reader can find in your report. Write the line after the work is done, and leave out impact or experience you cannot show.

Numbers to record while you work

Project name | tools, datasets and frameworks | link

Give the project a name of its own: “Ledger” is an example, not a label to copy. List the tools, datasets and frameworks you actually used, since several relevant ones show more than a single tool does. Hyperlink the last part to your published repository or report.

Turn your project into a portfolio piece

A project becomes easier to evaluate when someone can understand what you did, inspect the evidence, and follow your reasoning.

Create a short report, GitHub README, or portfolio page. A clear two-to-four-page report is a useful starting point, not a strict requirement.

Include:

1. Goal: What question or problem did you investigate?
2. Environment: What tools, practice data, or systems did you use?
3. Your work: What did you personally do, and why?
4. Evidence: Include useful screenshots, queries, code, or test results.
5. Findings: What did you discover? What remains uncertain?
6. Fix or recommendation: What should change, and did you test it?
7. Sources and limitations: Credit datasets and guides. Clearly identify simulated work.

Use sample or redacted information in the public version.

Publish the report somewhere accessible without requesting permission, and check the link before putting it on a résumé.

Put numbers in it

Count as you work, and put the figures in the report: records searched, findings confirmed, tests added, checks failing before and after. A reviewer can check every one of them against your evidence, which is exactly why they are worth including. Leave out business impact you cannot show.

Name it, then show your tools

A résumé line works best in three parts: your project’s own name, the tools and frameworks you used, and a link to the work. “Role-Based Access Lab” reads like a class exercise. A name plus a tool list tells a reviewer what you can actually work with, and every tool, dataset or framework you list honestly is another thing an interviewer can ask you about.

Project name | tools, datasets and frameworks | link

• Role-Based Access Lab→Turnstile | Keycloak, RBAC design, NIST SP 800-63, Docker | GitHub
• Login Hunt→Beacon | Python, pandas, Sigma, MITRE ATT&CK | GitHub
• Cloud Project→Bedrock | Terraform, Checkov, AWS IAM, CIS Benchmarks | GitHub

Why link a report?

Your résumé gives a short description of the project. The linked report lets a reviewer inspect your work and gives you concrete evidence and decisions to discuss during an interview.

Not every recruiter will open it, but it makes your work available for review.

Hyperlink the last part to the published work, so “GitHub” or “Project Report” opens your repository or report. Check the link before you send the résumé.

# Project title

> Practice project. Describe the simulated scenario, practice data, or lab used.

## Goal
What question or problem did you investigate?

## Environment
What tools, practice data, or systems did you use? Link datasets and guides.

## My work
What did you personally do, and why?

## Evidence
Screenshots, queries, code, or test results. Use sample or redacted information only.

## Findings
What did you discover?
The numbers behind it (records searched, findings confirmed, tests added).
What remains uncertain?

## Fix or recommendation
What should change, and did you test it?

## Sources and limitations
- Datasets and guides used:
- What was simulated:
- Limitations:

Related paths to explore

• Identity and Access Management

  Identity and access management (IAM) specialists decide how people sign in and what each account is allowed to reach, from the day someone joins until the day they leave.

• Threat Intelligence

  Threat intelligence analysts research who is attacking organizations, how, and why, then turn that research into practical guidance for defenders.

• Incident Response

  Incident responders take charge when a security incident is confirmed: they limit the damage, remove the attacker’s access, restore systems, and help the organization learn from what happened.