VCE Software Development U4O2 Word Scramble: Security controls for development practices and stored data and Threat modelling and evaluating security practices (Modules 49–72)
Name:
Date:
Class:
🔤
Word scramble
Unscramble the letters and write each key term on the line.
1
EDOC PIOSEYTROR
A central store for a project's source code and its version history, shared by a team through commits, branches, pull requests and access settings (private or public).
2
SEPROOTYRI CRTYIESU
Controlling who can read and change a code repository and protecting what is stored in it, e.g. private repos, roles, a protected main branch, no secrets in commits, audit logs.
3
EERP DECO WVRIEE
Another developer checks a change before it is merged, using a checklist that includes security checks, and approves it. The decision is recorded on the pull request.
4
ACTHP NMTAMAEGEN
The regular, planned process of finding, testing and installing updates that fix known vulnerabilities in software, including libraries and frameworks.
5
ESSRTEC EENTNMGMAA
Keeping passwords, API keys and tokens in a protected vault or environment variable, not in source code, and rotating keys and scanning commits for leaks.
6
HARTTE DLLNOIGEM
A structured way to work out what could go wrong with a system, before and during development, so risks are found, fixed and confirmed early and then reviewed again.
7
YITCRUES TMRQIEUNEER
A statement of the protection a system must provide for its data and functions, based on its assets, users and laws, written so it can be tested.
Answer Key
VCE Software Development U4O2 · Modules 49–72
1EDOC PIOSEYTROR → code repository — A central store for a project's source code and its version history, shared by a team through commits, branches, pull requests and access settings (private or public).
2SEPROOTYRI CRTYIESU → repository security — Controlling who can read and change a code repository and protecting what is stored in it, e.g. private repos, roles, a protected main branch, no secrets in commits, audit logs.
3EERP DECO WVRIEE → peer code review — Another developer checks a change before it is merged, using a checklist that includes security checks, and approves it. The decision is recorded on the pull request.
4ACTHP NMTAMAEGEN → patch management — The regular, planned process of finding, testing and installing updates that fix known vulnerabilities in software, including libraries and frameworks.
5ESSRTEC EENTNMGMAA → secrets management — Keeping passwords, API keys and tokens in a protected vault or environment variable, not in source code, and rotating keys and scanning commits for leaks.
6HARTTE DLLNOIGEM → threat modelling — A structured way to work out what could go wrong with a system, before and during development, so risks are found, fixed and confirmed early and then reviewed again.
7YITCRUES TMRQIEUNEER → security requirement — A statement of the protection a system must provide for its data and functions, based on its assets, users and laws, written so it can be tested.