LangSmith lifecycle & offboarding security checks
Dormant accounts, leavers with access, unowned assets and change-management gaps — the checks that catch what HR processes miss.
On LangSmith, Black Cat runs 3 checks in this area on every scan. Each one below lists its severity, how to fix it, and the compliance controls it satisfies where a control applies. See what access the LangSmith connector needs.
Checks (3)
severity: low LangSmith Agent Stale fix difficulty: easy #
Review stale agent projects
- Open LangSmith > Projects
- Review the project and determine if still needed
- Archive or delete if no longer active
Satisfies: NIS2 Directive NIS2-21.i.2 DORA (SaaS Security) DORA-9.6
severity: medium LangSmith Agent High Error Rate fix difficulty: medium #
Investigate and fix high error rate
- Open LangSmith > Projects > select the project
- Review failed run traces for common errors
- Fix error patterns and redeploy
Satisfies: NIS2 Directive NIS2-21.i.2 DORA (SaaS Security) DORA-9.6
severity: high LangSmith Agent Orphaned Owner fix difficulty: easy #
Reassign the LangSmith agent to an active owner
- Identify the agent owner in LangSmith
- Transfer ownership to an active team member
Satisfies: NIS2 Directive NIS2-21.i.2 DORA (SaaS Security) DORA-9.6