Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by WGU University
Exam Format
Registration
Validity
Skills this practice test covers
- Apply STRIDE to a software design and sort each threat into its category.
- Rate threats with DREAD and score vulnerabilities with CVSS.
- Choose between static analysis, dynamic analysis and fuzzing for a given test goal.
- Separate functional from non-functional security requirements, and plan a privacy impact assessment.
- Fit security activities into Waterfall, Agile and DevSecOps development.
- Compare BSIMM and OpenSAMM as ways to measure and improve a software security program.
Explore related topics
KEO1 exam content
4 domains · 0 topics · 289 questions
Security Methods within SDLC
This domain lays the groundwork: the security principles, standards and methods used across the SDLC, and how a security development lifecycle (SDL) differs from the SDLC itself. It also compares the main ways to test code for security.
Skills tested
- Explain how an SDL adds security activities to each phase of the SDLC.
- Use threat and vulnerability taxonomies such as the OWASP Top 10 and the CWE/SANS Top 25.
- Choose static analysis, dynamic analysis or fuzzing for a given testing goal.
- Apply defense in depth and security by design principles across the life cycle.
Software Requirements and Risk Assessment
This domain starts a project the secure way. Candidates gather security and privacy requirements, plan a privacy impact assessment, assign security roles, and adjust the work to Waterfall, Agile or DevSecOps teams.
Skills tested
- Separate functional security requirements from non-functional ones, with an example of each.
- Plan a privacy impact assessment and note GDPR and CCPA duties for personal data.
- Assign security duties with a RACI matrix, including the security champion and security architect roles.
- Explain how security work differs between Waterfall phases and Agile sprints.
Software Security Test Planning and Threat Modeling
This domain asks for a test plan that matches real threats. Candidates model threats with STRIDE, rank them with DREAD or PASTA, score vulnerabilities with CVSS, and choose test cases, test approaches, tools and code reviews.
Skills tested
- Map each STRIDE category to the security property it breaks, such as tampering to integrity.
- Rank threats with DREAD, and explain how PASTA ties them to business impact.
- Choose white box, gray box or black box testing for a given goal.
- Write security test cases tied to the risks, and plan peer code reviews.
Software Testing, Deployment, and Post-Release
This domain covers the end of the cycle: deciding whether software is ready to ship, keeping it secure after release, and improving the security program as a whole. It also compares maturity models such as BSIMM and OpenSAMM.
Skills tested
- Assess web application vulnerabilities, such as SQL injection, before a go/no-go decision.
- Plan post-release support with security monitoring, incident response and security updates.
- Explain why BSIMM suits benchmarking against other organizations and OpenSAMM suits planning improvement.
- Fit SDL activities into Waterfall, Agile and DevSecOps pipelines.
Requirements
- Required: enrollment in WGU's Master of Science in Cybersecurity and Information Assurance program.
- Required in the program: the two foundation courses that WGU sets before all later courses.
- Recommended: some programming experience and a basic understanding of networking.
About the KEO1 exam
KEO1 is the assessment for the Secure Software Design course (D487). The course belongs to the Master of Science in Cybersecurity and Information Assurance at Western Governors University (WGU). The assessment checks whether a student can keep software secure at every stage of the software development life cycle (SDLC), from requirements and risk to testing, release and support. The course stresses defense in depth across the whole cycle and adapts security work to Agile and DevSecOps teams. Passing gives credit for this course toward the degree; it is not an industry certification.
The test planning and threat modeling domain has the most questions in the PlanetCert practice test. STRIDE questions lead that domain. The explanations show why a threat belongs to one STRIDE category and not another, and why fuzzing finds different flaws from static analysis. Flashcard Mode suits the many models and frameworks, from DREAD and PASTA to BSIMM and OpenSAMM. Brainy AI Assistant can explain how a security development lifecycle (SDL) activity fits into an Agile sprint, or turn a missed requirements question into a fresh scenario.
How to earn the certification
- Earns
- Course credit for Secure Software Design toward WGU's Master of Science in Cybersecurity and Information AssuranceGraduate
The course credit counts toward the degree and needs no renewal.
How to prepare for KEO1
- 1
Map the four competencies first
WGU lists four competencies for this course: requirements and risks, test plans, testing and deployment, and security methods in the SDLC. Sort each textbook chapter under one of them before reading in depth.
- 2
Learn STRIDE until it is automatic
Write out the six STRIDE categories with the property each one breaks, then apply them to a simple login page. The test planning and threat modeling domain draws more practice questions than any other.
- 3
Scan a test site with OWASP ZAP
Scan a deliberately vulnerable web application with OWASP ZAP and read each alert. The course labs work with findings like these, and the deployment domain asks how they affect a release decision.
- 4
Put the frameworks in one table
List BSIMM, OpenSAMM, Microsoft SDL, STRIDE, DREAD and PASTA with the purpose of each and when it is used. Mixing up two of them, such as BSIMM and OpenSAMM, is a common cause of missed questions.
- 5
Take the pre-assessment, then go timed
WGU's pre-assessment shows which competency needs more work. Then run the KEO1 practice test in Timed Mode, and ask Brainy AI Assistant to explain any requirement or threat question that went wrong.
Start a timed KEO1run
WGU's course materials center on the textbook Practical Core Software Security, with labs on assessing web application vulnerabilities and analyzing assessment tool output.
Who KEO1 is for
- WGU graduate students in the Master of Science in Cybersecurity and Information Assurance.
- Software developers in the program who are adding security to their daily work.
- Security professionals in the program who are moving into secure coding and application security.
Typical job titles: Application security engineer · Software developer · Security analyst · Security architect · DevSecOps engineer
KEO1 glossary
18 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Black box testing
- Testing with no knowledge of the code or design, the way an outside attacker sees the system.
- BSIMM
- Building Security In Maturity Model: a study of real software security initiatives that lets an organization compare its practices with others.
- Common Vulnerability Scoring System (CVSS)
- An open standard that gives a vulnerability a severity score from its base metrics, which environmental metrics can adjust.
- Defense in Depth
- Using several layers of security controls, so that one failed control does not expose the whole system.
- DREAD
- A risk rating model that scores a threat on damage potential, reproducibility, exploitability, affected users and discoverability.
- Dynamic Analysis
- Testing a program while it runs, to find flaws that only show up at runtime.
- Functional security requirements
- Requirements for security features the software must have, such as authentication or access control.
- Fuzzing
- Sending large amounts of random or malformed input to a program to make it crash or misbehave.
- Gray box testing
- Testing with partial knowledge of the system, such as its design documents but not its full source code.
- Non-functional security requirements (NFRs)
- Requirements for qualities of the software, such as availability or auditability, instead of features a user sees.
- OpenSAMM
- The OWASP Software Assurance Maturity Model: a framework for planning and measuring step-by-step improvement in software security.
- OWASP ZAP
- An open-source scanner that tests running web applications for vulnerabilities, a common tool for dynamic analysis.
- Privacy Impact Assessment (PIA)
- A review of how a system collects, uses and protects personal data, done early to find privacy risks.
- Process for Attack Simulation and Threat Analysis (PASTA)
- A risk-centric threat modeling method that simulates attacks and ties each threat to its business impact.
- Security champion role
- A developer on the team who takes extra responsibility for security and links the team with security specialists.
- Security Development Lifecycle (SDL)
- A set of security activities added to each phase of software development, from requirements to release and support.
- Static Analysis
- Checking source code for security flaws without running the program.
- STRIDE
- A threat model that sorts threats into six types: spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege.