Your team is preparing for a SOC 2 review and wants to understand how changes reach its public website. Duo can inspect the repository and GitLab records, identify relevant controls, and narrow the questions that need someone's input. Start with the project and a short description, then use the findings to guide a closer look at one change.
Open a conversation in your project
Use an existing GitLab project that builds a website through CI/CD, with at least one merged change and a pipeline to examine. You'll need access to its code and records, security scanning enabled, and the Security Analyst agent available. The Security Analyst setup instructions cover availability and enabling foundational agents.
Open that project in GitLab. In the GitLab Duo sidebar, select Add new chat, then Security Analyst.
The example below follows a public cookbook website. Replace that description with your own site's purpose if needed. You can begin with what the application does; let Duo identify the relevant files, records, and requirements as it investigates.
Start with the existing prompt
This fills the original prompt's standard and implementation placeholders:
@security_analyst Check if this implementation meets SOC2:
The public cookbook website in this GitLab project: how changes are validated and deployed. Review the implementation on the current default branch. This is an assessment only; do not change files or settings.
Verify:
1. Data handling requirements
2. Access control standards
3. Audit logging needs
4. Encryption requirements
5. Documentation completeness
Let Duo work through the project before preparing more material. Look at the sources it reads and the findings it connects to them. Your project's pipeline, deployment setup, and available records will shape the answer.
Read the findings alongside their sources
Open a source link for a finding that matters to your team. These comparisons help you judge what it establishes:
| Finding to examine | What to look for |
|---|---|
| Validation happens before deployment. | The CI jobs, stages, and rules explain the configured behavior. A pipeline shows which jobs were included and their results; compare it with the rules to explain jobs that are absent or skipped. |
| Changes receive independent review. | Approval records can show who approved a change. The person who merged it and the people assigned as reviewers don't, by themselves, establish whether approval happened. |
| The website is released through a particular path. | A deployment record tied to a commit helps establish what was released. For GitLab Pages, look at the publish job and Pages deployment details as well as environment records. An older MR describing a local deployment may leave the current process unresolved. |
For example, a pipeline file may put tests before deployment while a path filter skips those tests for some changes. Duo can investigate that relationship and find a pipeline that illustrates it. The remaining question might concern a separate release system or an approval process whose records aren't available in the project.
These are checks on the findings Duo produces. You can ask it to retrieve the supporting records before spending time gathering them yourself. If it gives a broad compliance label, bring the conversation back to the specific controls and records behind that conclusion.
Follow one change through the process
Continue the same conversation with:
Choose one recent merged change to this site and trace how it was validated and released. Inspect the CI job rules, that change's pipeline and approval records, and any deployment record you can access. Show the links supporting each finding.
Separate configured checks from checks that actually ran, and recorded approvals from the identity of the person who merged. Explain any gaps you can establish and list the questions you couldn't answer from available records. Keep this as an assessment without changing files or settings.
Look for a trace you can follow from the MR and commit to its validation, approvals, and release evidence. Check that the linked records refer to the same change. A successful pipeline shows what passed in that run; identifying the released commit may require a deployment record from another system. An inaccessible record leaves a question open.
Keep claims about review quality tied to the available records. A short review comment may document only part of the work someone did. If a search returns no deployment record, check which system and records it covered before concluding that no release occurred.
If Duo stops at a generic checklist or asks you to copy files it can read, direct it back to the project's available sources. When it reaches settings or records it can't access, use its explanation to identify the specific information or owner needed to continue.
Take the findings into your review
You should now have concrete observations with source links, proposed next actions, and a smaller set of unanswered questions. Review the recommendations with the people responsible for the implementation and compliance requirements. Keep the supporting records with each finding so someone else can check the reasoning.
The value of the conversation is the investigation Duo completes: finding relevant files, connecting configuration to records, and helping you decide what needs attention. Your remaining work is to judge those findings and supply the context that the available project records couldn't provide.