
Omar received production access on May 2, 2025. His awareness record is dated May 5, 2025.
What must be checked before this access can be treated as compliant?
The May 5 date must be compared with the access rule. The record must also contain the required evidence.
Security testing and awareness combines communication with checks. Security teams tell employees and contractors how to protect systems, data, and credentials. They also explain how to report suspicious events.
Reviewers and service auditors inspect training records, access logs, policy versions, and change records. The central question has three parts. Did the right people receive the required communication on time? Does evidence support the result? Does the result belong in the stated report scope?
Risk and policy define who must learn what. The awareness requirement sets the timing and evidence. The walkthrough compares each condition with records. The report boundary identifies the systems, users, dates, and criteria that count. The final result records any deficiency and supports the assessment report.
Loading diagram…
A sound report result depends on every earlier link. Correct training rules cannot support a conclusion when the walkthrough uses wrong evidence. Correct evidence cannot support a conclusion about a system outside report scope.
Security awareness training communicates expected behavior, responsibilities, secure information handling, and reporting routes for suspicious events. NIST SP 800-53 Rev. 5, AT-2 requires security and privacy literacy training during initial training for new users. It also covers required system changes and an organization-defined frequency.
NIST does not create a universal 12-month refresh rule. The documented case policy sets the concrete rules. Initial training must occur before access. A refresh is required every 12 months. Change training is required within 10 business days after a significant change.
NIST SP 800-50 supports a broader awareness and training program. TSC CC2.2 supports communication of objectives and responsibilities needed for internal control. Further detail on purpose and communication is in Awareness training and policy walkthroughs.
Start with the policy's covered population. Then inspect the access authorization log, training register, policy or course version, and change record.
Test the conditions in order:
A missing required field does not support a pass. A late change-training event is separate from initial training. If initial timing passed, a late change result does not rewrite it. The detailed condition-by-condition procedure is in Awareness training and policy walkthroughs.
A SOC 2 Type 1 report addresses control design and implementation as of a specified date. A SOC 2 Type 2 report also addresses operating effectiveness over a specified period.
Report input must connect the system description and management assertion to the Trust Services Criteria. It must also connect in-scope controls, the date or period, test procedures, evidence, and exceptions.
Evidence from a system outside the stated scope cannot support an in-scope conclusion. The report and scope treatment is in Assessment reports and control deficiencies.
A design deficiency exists when the control does not address the relevant risk. An operating deficiency exists when the required control step was not followed. Training after access is one example.
An evidence gap means the reviewer cannot support a pass. The missing record alone may not prove that the control failed. A scope mismatch is corrected as a report-boundary problem unless evidence shows a separate control failure.
TSC CC4.2 requires internal control deficiencies to be evaluated and communicated promptly to those responsible for corrective action. TSC CC5.3 supports control activities that address risks. The deficiency and reconciliation treatment is in Assessment reports and control deficiencies.
The carried artifact is a requirement-to-evidence trace. It records the policy requirement, covered population, access and training dates, significant-change date and due date, required evidence fields, condition result, exception, and report conclusion.
If the scope is wrong, evidence may support the wrong system. If a date is wrong, late completion may look timely. If missing evidence is treated as a pass, the report is unsupported. If a scope mismatch is labeled as a control failure, the report records the wrong problem.
The same attributes separate the communication requirement, testing procedure, report boundary, and deficiency. This comparison identifies the question answered by each idea and the evidence needed.
| Idea | Trigger | What is received | What is recognized | Time limit | Basis | Output |
|---|---|---|---|---|---|---|
| Awareness requirement | New user, significant change, or recurring refresh | Risk, policy, role, and reporting information | Required behavior and training obligation | Before access; every 12 months; within 10 business days after significant change | NIST AT-2, TSC CC2.2, and documented policy | Training assignment and record |
| Walkthrough | Review of a documented security procedure | Policy criteria, population, access records, training records, change records, and evidence fields | Pass, fail, or unsupported result for each condition | Test each listed condition in order | Documented policy and source evidence | Requirement-to-evidence trace |
| Assessment report input | SOC 2 control within engagement scope | System description, assertion, criteria, period, controls, procedures, evidence, and exceptions | Whether the report statement is supported for the stated scope and date or period | Type 1 as of a specified date; Type 2 over a specified period | AICPA Trust Services Criteria and SSAE-18 AT-C 105 and AT-C 205 | Draft report result |
| Control deficiency | Failed design, failed operation, incomplete evidence, or inconsistent scope | Exception, risk link, policy basis, and supporting records | Deficiency, evidence exception, or scope correction | Communicate deficiencies timely under TSC CC4.2 | TSC CC4.2, CC5.3, and evidence | Corrected result and deficiency communication |
The rows separate a scope correction from an operating exception. Those results require different report treatment.
CloudLedger's draft SOC 2 Type 2 report covers January 1 through December 31, 2025. The draft system description names Payroll Core and MobilePay. The engagement scope schedule and control evidence cover Payroll Core only.
Management confirms that MobilePay was not offered during the report period. The security awareness policy is effective January 1, 2025.
The policy requires:
Payroll Core has 40 privileged users. All other 39 users met all conditions.
Priya received access on February 3, 2025. She completed initial training on February 5, 2025. A significant change occurred on March 3, 2025. She completed change training on March 20, 2025. The policy calendar due date was March 17, 2025.
What scope correction and control result should enter the report?
The schedule applies the awareness rule, tests each date and evidence condition, corrects the report boundary, and records the operating exception.
| Step | Work | Case result | Source chapter |
|---|---|---|---|
| Set the rule | Apply NIST AT-2 and the CloudLedger policy. Initial training is before access. Refreshes occur every 12 months. Change training is within 10 business days. Required evidence fields are present. | These conditions define the walkthrough. | Awareness training and policy walkthroughs |
| Walk through Priya | Compare February 3 access with February 5 initial training. Compare the March 17 due date with March 20 completion. Inspect required evidence fields. | Initial timing fails and change-training timing fails. The results remain separate. | Awareness training and policy walkthroughs |
| Fix the report boundary | The description includes Payroll Core and MobilePay. The scope schedule and evidence cover Payroll Core. Management says MobilePay was not offered during the period. | Revise the description to Payroll Core. Make no conclusion on MobilePay. | Assessment reports and control deficiencies |
| Report the control result | The population is 40 users. The other 39 users met all conditions. Priya is one exception. Record the policy, dates, evidence, population, and test result. | Report one operating exception or deficiency, not 40 passes and not a MobilePay result. The auditor evaluates the effect on the report. | Assessment reports and control deficiencies |
A user received access on July 7, 2025. The user completed training on July 6, 2025. The record has no course-version field.
Can the walkthrough mark the record as passed?
Answer: Initial timing is supported, but the missing required field is an evidence exception, so the complete record cannot be marked passed.
The main case changes only one fact. Priya's initial training date is February 2, 2025. Every other fact remains unchanged.
Which walkthrough result changes?
Answer: Initial timing now passes, change-training timing still fails because March 20 is after March 17, and Priya's overall record remains an exception.
The questions change one fact at a time across timing, evidence, scope, and control results.
Practice
A policy uses the case deadlines: initial training before access, a refresh every 12 months, and change training within 10 business days after a significant change. A user's access began August 4, 2025; initial training was completed August 3, 2025. A significant change occurred November 3, 2025; the change course was completed November 20, 2025, and the policy due date was November 17, 2025. What is the correct walkthrough result?
The policy requires a user ID, course version, completion timestamp, and acknowledgment in the training record. A register contains the user ID, course version, and completion timestamp, but no acknowledgment. What should the reviewer record?
A draft SOC 2 Type 2 report covers January 1 through December 31, 2025. Its system description names Payroll Core and MobilePay, but the engagement scope schedule and evidence cover Payroll Core only. Management confirms MobilePay was not offered during the report period. What report input is correct?
An assessment covers 40 privileged Payroll Core users. One user received access on February 3, 2025, and completed initial training on February 5, 2025. All other users met the requirements and all records have the required evidence. Which input is correct?
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more
1. A company maintains daily backups in storage that production administrators cannot alter or delete during a 30-day retention period. If ransomware encrypts production files, which control objective is primarily supported by this configuration?
Answer: A. Restoring reliable data after the affected systems are contained
Restoring reliable data after the affected systems are contained - Daily backups provide copies from which the company can restore production files encrypted by ransomware. - Preventing production administrators from altering or deleting those copies during the 30-day retention period helps preserve a reliable recovery source after the affected systems are contained. Preventing users from disclosing credentials to a fraudulent website - Protected backups do not stop a user from entering credentials on a fraudulent website. - That risk calls for measures such as phishing awareness and phishing-resistant authentication, rather than backup retention. Detecting unauthorized changes to production application code - The configuration protects stored backup copies; it does not monitor production application code for unauthorized changes. - Code-integrity monitoring or change-management controls address that detection objective. Limiting collection of personal data to approved business purposes - A 30-day backup retention period governs how long these backup copies are protected, not what personal data the company collects. - Limiting collection to approved purposes is a privacy objective addressed through purpose-limitation and data-minimization controls.
2. A company applying the NIST Cybersecurity Framework 2.0 inventories its information systems, maps the personal data processed by each system, identifies critical suppliers, and documents related cybersecurity risks. Which framework function is primarily addressed by these activities?
Answer: A. Identify
Identify - Inventories of information systems and maps of personal data establish what the company has and processes, which falls under the NIST Cybersecurity Framework 2.0 Identify function. - Identifying critical suppliers and documenting related risks establish where cybersecurity exposure lies, rather than implementing or operating a safeguard. Protect - Protect concerns safeguards, such as access controls and data security measures, for systems and information already identified. - The company is mapping personal data and documenting risks, not describing controls that secure that data. Detect - Detect concerns discovering and analyzing cybersecurity events through activities such as monitoring. - Inventorying systems and identifying suppliers may inform monitoring, but neither activity discovers an event. Recover - Recover concerns restoring affected operations after a cybersecurity incident. - The stem describes understanding systems, suppliers, and risks before an incident, not restoring services afterward.
3. Developers need realistic records to test boundary conditions in a new claims application. The proposed test database would be a production copy containing names, Social Security numbers, and medical claim details. Screen masking would hide these fields, but developers could directly query the database. Which control best reduces confidentiality risk while preserving the required testing capability?
Answer: A. Generate synthetic records that preserve production formats and boundary conditions
Generate synthetic records that preserve production formats and boundary conditions - Synthetic records can reproduce the formats and boundary conditions developers need without placing real names, Social Security numbers, or medical claim details in the test database. - Unlike screen masking, which developers could bypass by querying the database directly, synthetic data removes actual individuals’ sensitive information from those queries. Encrypt the production copy at rest while granting developers decryption access - Encryption at rest protects the stored copy, but developers granted decryption access can still retrieve its production data. - It therefore leaves real names, Social Security numbers, and medical claim details available during testing. Log developer database queries and review the logs at the end of each month - Monthly log review may detect inappropriate queries only after developers have accessed confidential information. - It does not keep sensitive production records out of the test database or prevent direct queries. Require developers to sign confidentiality agreements before accessing the copy - Confidentiality agreements impose an obligation on developers but do not restrict what their database queries can retrieve. - The proposed copy would still contain real names, Social Security numbers, and medical claim details.
4. A state privacy requirement permits an employer to collect fingerprint templates for facility access but requires retention only as long as reasonably necessary for the disclosed purpose, unless a legal hold applies. The employer encrypts the templates but plans to retain them indefinitely after employees leave. Which change best addresses the deficiency?
Answer: B. Delete templates under a documented schedule tied to separation and legal holds
Delete templates under a documented schedule tied to separation and legal holds - A documented deletion schedule ends retention when fingerprint templates are no longer reasonably necessary for facility access after separation. - The schedule can preserve templates subject to a legal hold, as the state requirement permits. Add multifactor authentication for administrators who manage the templates - Multifactor authentication limits unauthorized administrator access but does not set a retention period. - The employer would still retain former employees’ templates indefinitely. Conduct quarterly vulnerability scans of the biometric access-control servers - Vulnerability scans identify server weaknesses, not whether templates are deleted when their disclosed purpose ends. - Quarterly scanning leaves the indefinite-retention plan unchanged. Store an additional encrypted copy of each template at a recovery site - A recovery copy supports availability but does not address deletion after employees leave. - Encryption and an additional copy do not justify retaining templates indefinitely.
5. Linden Billing Services, Inc. processes customer billing data for retailers. On June 3, 2026, Linden discovered that an employee's unencrypted company laptop had been lost while traveling. A CPA on Linden's incident-response team must assess the available evidence, determine the affected population, apply contractual and State X notification criteria, and document the response. Assume all times are local, there was no active exfiltration when the incident was detected, and no law-enforcement delay was requested.
6. A company expects a distributed denial-of-service attack against its public customer portal. Management's objective is to maintain availability by preventing a surge of requests from exhausting the portal's processing capacity. Which control best addresses this risk?
Answer: B. Using traffic scrubbing, rate limiting, and geographically distributed capacity
Using traffic scrubbing, rate limiting, and geographically distributed capacity - Traffic scrubbing filters malicious requests, while rate limiting restricts how many requests reach the portal. - Geographically distributed capacity helps absorb a request surge before it exhausts processing resources, directly supporting the availability objective. Encrypting customer records stored by the portal - Encryption protects the confidentiality of stored customer records. - It does not reduce incoming request volume or keep the portal’s processing capacity from being exhausted. Requiring multifactor authentication for portal administrators - Administrator multifactor authentication reduces the risk of unauthorized administrative access. - It does not control the surge of public requests expected in a distributed denial-of-service attack. Reviewing application logs after the portal becomes unavailable - Log review can help investigate the attack and its effects. - Reviewing logs after the outage cannot prevent the request surge from making the portal unavailable.
7. Harbor Health Clinic maintains a cloud export containing patient health records. On January 6, 2026, security monitoring identified unauthorized activity involving the export. Management must determine the scope of the incident, apply the supplied federal HIPAA breach notification requirements, preserve evidence, and document the incident-response conclusion. Use Exhibits 1 through 4 to complete the tasks.
1. What are key objectives of internal controls?
Internal controls aim to ensure reliable financial reporting and compliance with applicable laws and regulations; they also enhance the effectiveness and efficiency of operations and safeguard assets.
2. What is the purpose of a field check in data entry?
A field check prevents invalid characters from being entered into a data field. For example, it ensures that only numbers are entered in a Social Security number field.
Get full Oncourse access with lessons, practice questions, flashcards and AI study tools.
Scan to download app
Enter your email to get your 75% OFF code and unlock the full CPA question bank on the app.