CY0-001 Premium Exam Questions

Basic Concept: Dynamic Application Security Testing (DAST) tests running applications by sending various inputs to discover vulnerabilities. AI can significantly enhance DAST by intelligently generating diverse, targeted test payloads that traditional tools might miss. CompTIA SecAI+ covers AI augmentation of security testing methodologies.

Why C is Correct: Payload creation is highly suitable for AI automation during DAST. AI can generate diverse, contextually appropriate attack payloads such as SQL injection strings, XSS vectors, command injection attempts, and format string exploits tailored to the specific application ' s behavior observed during testing. AI can learn from the application ' s responses to previous payloads and generate increasingly targeted inputs, discovering vulnerabilities more efficiently than static payload databases.

Why A is Wrong: DDoS attacks are volume-based attacks designed to overwhelm network or application infrastructure. Automating DDoS during DAST is inappropriate as it would disrupt service availability rather than discover application security vulnerabilities, and it is harmful to legitimate operations.

Why B is Wrong: Data poisoning is an attack targeting AI/ML model training data integrity. It is relevant to securing AI systems but is not a DAST technique for testing web or software application security vulnerabilities during dynamic testing.

Why D is Wrong: Threat modeling is a structured analysis process performed before development or testing to identify potential threats and design appropriate countermeasures. It is a planning activity, not an attack technique that can be automated during dynamic application security testing.

Basic Concept: Adding validation layers to software development processes improves security assurance by catching issues that human reviewers might miss. AI-assisted validation provides an automated, systematic review that complements human judgment. CompTIA SecAI+ Study Guide covers AI-assisted development security controls.

Why A is Correct: AI-assisted approval adds an intelligent automated review layer that works alongside existing human review. AI can systematically analyze code for security vulnerabilities, coding standard violations, dependency risks, and policy compliance with greater consistency and speed than manual review. This creates a defense-in-depth validation approach where both AI and human reviewers must approve changes, catching issues that either layer might miss independently.

Why B is Wrong: A low-code plug-in provides simplified visual development tools that reduce the amount of manual code writing required. It is a development productivity tool, not a security validation layer for reviewing already-written code.

Why C is Wrong: Automated rollback is a deployment safety mechanism that reverts a deployment to the previous version when errors are detected after deployment. It is a recovery control, not a validation layer applied during the development review process.

Why D is Wrong: Regression testing verifies that new code changes have not broken existing functionality. It tests functional correctness, not security vulnerabilities, and does not add an AI-powered security validation capability to the existing human review process.

Option D is correct because the failure is an authorization problem: every external customer can receive sensitive information even though only some customers are permitted to use it. Role-based access control assigns permissions to defined customer roles and requires the API to evaluate the caller’s role before returning protected fields or invoking sensitive model functions. Properly implemented, RBAC supports least privilege and separates ordinary customers from approved sensitive-data users. Option A may route customers to different models, but model selection does not itself enforce who is authorized to receive data. Option B changes model behavior and training data, yet retraining cannot replace an access-control decision at the API boundary. Option C may improve network isolation, but placing the model in a VPC does not stop an authenticated external customer from receiving information that the API exposes. The organization should also apply field-level filtering, deny-by-default policies, logging, and authorization testing. NIST’s RBAC model assigns users to roles and associates each role with permitted privileges, directly supporting this control.

================

Option D is correct because behavioral anomaly detection requires a persistent baseline of normal user activity and a repeatable method for measuring departures from that baseline. Automated playbooks can continuously collect authentication, endpoint, network, and application events, calculate deviations such as unusual login times, abnormal resource access, or atypical transaction volume, and escalate activity that exceeds defined thresholds. Standard-deviation-based comparison is broader and more defensible than searching for a username or checking a single data source. Option A provides only a permissions comparison at one point in time; it does not establish how the user normally behaves. Option B searches log occurrences but lacks behavioral context, trend analysis, and reliable anomaly scoring. Option C observes only browser activity and therefore misses anomalies in identity, host, cloud, and business systems. A mature implementation should tune baselines, account for role and seasonality, and retain analyst review so legitimate changes are not treated as malicious. This aligns with AI-assisted security concepts involving user and entity behavior analytics, automated enrichment, and risk-based triage.

================