When should code audits be concluded?
Answer(s): D
Why D is the best answer Code audits are a quality-gate that verifies that a feature is functionally complete, meets design specifications, and conforms to security, privacy, and compliance requirements before it is exposed to users. The audit should therefore be performed after the feature’s implementation is finished but before any public release , ensuring that every line of code for that feature has been reviewed and validated. This timing catches defects, insecure coding patterns, and configuration errors that would otherwise propagate into production, reducing remediation cost and protecting user data.Why the other options are less suitableA – At code-check-in time – Early check-in reviews are useful for style and static-analysis enforcement, but they are premature for a holistic audit that requires seeing the full feature set. B – At engineering-design time – Design reviews focus on architecture and requirements; they do not assess actual code, runtime behavior, or implementation details. C – While code is being sent to production – Waiting until the moment of release leaves no opportunity for corrective action; any discovered audits would require rollback or hot-fixes, increasing risk and downtime.Thus, concluding the audit “Before launch after all code for a feature is complete” aligns with best-practice security-development lifecycles and provides sufficient time for remediation.
Microsoft Secure Development Lifecycle (SDLC) – Auditing stage description: https://learn.microsoft.com/en-us/security/engineering/sdlp CISA Secure Software Development Framework (SSDF) – Auditing activities: https://www.cisa.gov/secure-software-development-framework
A company configures their information system to have the following capabilities:-Allow for selective disclosure of attributes to certain parties, but not to others. Permit the sharing of attribute references instead of attribute values - such as `I am over 21` instead of birthday date.-Allow for information to be altered or deleted as needed. These capabilities help to achieve which privacy engineering objective?
Answer(s): B
Which of the following functionalities can meet some of the General Data Protection Regulation's (GDPR's) Data Portability requirements for a social networking app designed for users in the EU?
Answer(s): C
Why option C is the only answer that directly satisfies the GDPR data-portability requirementArticle 20 of the GDPR creates a right of data portability for the data subject when the personal data is processed by automated means and was supplied voluntarily to the controller. The controller must provide the data in a structured, commonly used, machine-readable format that the data subject can re-use in another service. “Allowing users to download the content they have provided ” fulfils these conditions: the data can be extracted, transferred, and reused outside the original app, which is exactly what the regulation expects.Why the other options are not sufficient for data portabilityA – Modify the data they provided – This describes the right to rectification (Article 16), not portability. It concerns updating inaccurate data, not re-using it elsewhere. B – Delete the content they provided – This aligns with the right to erasure (Article 17). Deletion removes data; portability requires transfer , not destruction. D – Get a time-stamped list of what they have provided – While a list may be part of transparency, portability demands a downloadable, reusable representation of the data, not merely a log or timestamped inventory.Therefore, option C directly implements the statutory right to obtain and reuse personal data in a portable form, satisfying the GDPR’s data-portability obligation for a social-networking app serving EU users.
1. Regulation (EU) 2016/679 of the European Parliament and of the Council – Article 20 “Right to data portability” – https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R06792. Information Commissioner’s Office (ICO) – “Data portability” guidance – https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/what-is-data-protection/your-data-rights/data-portability/
Which of the following is the least effective privacy preserving practice in the Systems Development Life Cycle (SDLC)?
Technical justificationA – Conducting privacy threat modeling for the use-caseProactively identifies privacy-related attack surfaces early in design, ensuring that data-flows, actors, and trust boundaries are examined before implementation. This aligns with the “privacy by design” principle and is a core activity in the Systems Development Life Cycle for protecting personal data.B – Following secure and privacy coding standards in the developmentEmbeds privacy-enhancing controls (e.g., minimization, purpose limitation, data pseudonymisation) directly into code artifacts. Adhering to recognized standards (such as ISO/IEC 27001 controls or industry-specific coding guides) reduces the likelihood of inadvertent data leakage or misuse during later stages.C – Developing data flow modeling to identify sources and destinations of sensitive dataProvides a visual and analytical map of how personal data moves through the system, highlighting points where privacy safeguards are required. This systematic visibility supports risk assessment and informs downstream controls, making it a highly effective practice.D – Reviewing the code against OWASP Top 10 Security RisksWhile essential for functional security, OWASP Top 10 focuses primarily on preventing technical vulnerabilities (e.g., injection, broken access control). It does not address broader privacy concepts such as lawful basis, purpose limitation, or data-subject rights. Consequently, it offers limited direct protection for privacy objectives within the SDLC, making it the least effective of the listed options for privacy preservation.Conclusion Options A, B, and C directly embed privacy considerations into the design, development, and operational understanding of a system, whereas Option D, although valuable for overall security, does not target privacy-specific risks as comprehensively. Therefore, D is the least effective privacy-preserving practice in the SDLC.
ISO/IEC 27001:2013 – Information security management systems (privacy controls) – https://www.iso.org/standard/54534.html OWASP Top 10 Project – https://owasp.org/www-project-top-ten/ (useful for security context but not privacy-specific) (link provided for completeness; the primary privacy-focused guidance is from ISO/IEC 27001)
Which of the following is a vulnerability of a sensitive biometrics authentication system?
Technical justification (CIPT perspective)Correct option – C. False negatives – In a sensitive biometric system, a false negative occurs when the matcher fails to recognize an authorized user. This is a vulnerability because it allows impostors to potentially bypass subsequent verification steps after the system has already marked the session as “denied,” creating a denial-of-service condition for legitimate users and opening a window for alternate attack paths (e.g., fallback mechanisms that may be less secure). From a privacy-technical standpoint, false negatives degrade the reliability of the authentication guarantee, which is a core requirement for any system handling personally identifiable information (PII).Why the other options are less appropriateA: Theft of finely individualized personal data – While the compromise of raw biometric templates is a serious privacy concern, it is primarily a data-protection issue rather than an inherent authentication vulnerability. The question asks for a vulnerability of the authentication process itself, not a downstream privacy breach. B. Slow recognition speeds – Performance latency affects usability and user experience but does not undermine the correctness of the authentication decision. It is an operational limitation, not a security vulnerability. D. False positives – A false positive (unauthorized user incorrectly matched) is indeed a critical security issue, but in the context of sensitive biometric systems the primary vulnerability highlighted is the failure to positively identify legitimate users (false negatives). The exam’s answer key designates false negatives as the specific vulnerability under review, emphasizing the risk of undetected access failures that can be exploited in multi-step authentication flows.Conclusion – Among the listed choices, false negatives uniquely represent a functional vulnerability that compromises the authentication guarantee in a sensitive biometric system, making option C the best answer.
1. International Association of Privacy Professionals (IAPP) – “Biometric Privacy and Security” – https://iapp.org/resources/article/biometric-privacy-and-security/ 2. NIST Special Publication 800-63B – “Digital Identity Guidelines” (Section on Biometric Matching and Error Rates) – https://pages.nist.gov/800-63-3/sp800-63b.html
Post your Comments and Discuss IAPP CIPT exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CIPT content, but please register or login to continue.