Answer: Devin users should take precautions with Devin-written code such as code reviews and enabling branch protections to ensure checks are enforced before Devin can merge any changes, and should store credentials securely using the Secrets feature under the Settings page. Status: Confirmed Entry: tool/devin/permissions-and-security/user-security-best-practices Revision: 1 Digest: sha256:b5d888be558c4d96 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:12:27Z Last changed: 2026-11-13T03:12:27Z Last verified: 2026-11-20T12:41:25Z Next check: 2026-11-21T12:41:25Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Code review practice | code reviews | [1] | 2026-11-20 Branch protections | enabling branch protections to ensure checks are enforced before Devin can merge any changes | [1] | 2026-11-20 Secrets storage | Secrets feature under the Settings page | [1] | 2026-11-20 Security incident email | security@cognition.ai | [1] | 2026-11-20 Sources: [1] Cognition. "Security at Cognition". https://docs.devin.ai/admin/security.md Role: primary. Accessed: 2026-11-20T12:41:25Z Quote: "we recommend taking the appropriate precautions with the code written by Devin such as code reviews" (Supports: Code review practice) Quote: "enabling branch protections to ensure checks are enforced before Devin can merge any changes" (Supports: Branch protections) Quote: "leverage our Secrets feature under the Settings page to share and store those credentials securely" (Supports: Secrets storage) Quote: "reporting incidents by emailing [security@cognition.ai](mailto:security@cognition.ai)" (Supports: Security incident email) Published: 2026-11-20T09:56:15Z Snapshot SHA-256: 9846a106bd8ec815f87e70955aed0f3fd82563a16c43bc0b7db443cb115772e5 (captured 2026-11-15T12:44:07Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-15T12:44:09Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:41:25Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:41:25Z Last attempt: 2026-11-20T12:41:25Z Notes and limitations: Extracted automatically from a single official source (section "User Best Practices"). Related: https://latestn.com/tool/devin/permissions-and-security/vpn-credentials-and-profile-files Where do I store Devin VPN credentials and how does Devin access the VPN profile file? https://latestn.com/tool/devin/pricing-and-limits/accepted-payment-methods What payment methods does Devin accept for paid plans? https://latestn.com/tool/devin/pricing-and-limits/active-users-rate-limit What is the rate limit for the Devin Get Active Users endpoint? https://latestn.com/tool/devin/permissions-and-security/tool-calls-authentication How do I authenticate requests to the Devin agent tool calls endpoint? https://latestn.com/tool/devin/permissions-and-security/usage-config-service-key-permissions What permissions does the Devin service key need to call Get Usage Configuration? https://latestn.com/tool/devin/permissions-and-security/user-page-analytics-service-key-permissions What service key permissions does Devin require to call the User Page Analytics API? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:12:27Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/permissions-and-security/user-security-best-practices/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/permissions-and-security/user-security-best-practices POST: https://latestn.com/dispute/tool/devin/permissions-and-security/user-security-best-practices with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/permissions-and-security/user-security-best-practices?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What security best practices should Devin users follow? Revision 1, last verified 2026-11-20T12:41:25Z. https://latestn.com/tool/devin/permissions-and-security/user-security-best-practices (accessed 2026-11-21T10:02:43Z). @misc{LatestN_tool_devin_permissions_and_security_user_security_best_practices_r1, title = {What security best practices should Devin users follow?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/permissions-and-security/user-security-best-practices}}, note = {Revision 1; digest sha256:b5d888be558c4d96; last verified 2026-11-20T12:41:25Z; accessed 2026-11-21T10:02:43Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/permissions-and-security/user-security-best-practices