- Revenus de retraite et stratégie de décaissement
- Fiscalité : Roth/RRSP, récolte de pertes, évolutions réglementaires
- Succession, assurance et planification transfrontalière
- Outils du conseiller : préparation des rendez-vous, pré-contrôle de conformité
21 500+ compétences et agents. Tous gouvernés.
5,814 agents prêts à l'emploi et 15,654 compétences de bibliothèque couvrant 24 secteurs et 12 métiers par secteur — installables depuis le catalogue, connectés à vos systèmes et exécutés à travers la même chaîne de contrôles en échec fermé que tout le reste sur Cortex.
21,511 modèles de bibliothèque dans la matrice du catalogue
Partez d'une collection sélectionnée.
Des suites conçues à la main pour les tâches que les entreprises automatisent en premier — chaque collection est livrée gouvernée, politiques et audit inclus.
- Service, ventes et customer success
- Service desk IT, RH et finance ops
- Réception juridique, achats et opérations terrain
- Risque et conformité
- Tri de la boîte de réception et rédaction d'e-mails
- Préparation de réunions, notes et suivi
- Planification intelligente et briefing quotidien
- Orchestration d'assistant de direction
- Sinistres intelligents, actuariat et AML
- Audit, GRC et reporting ESG
- ITAM / ITSM et opérations de sécurité
- Ateliers data et analytics
Trouvez la compétence dont votre équipe a besoin.
Recherchez parmi 21,500+ compétences et agents gouvernés, ou filtrez par secteur et par type : chaque résultat s'installe depuis le catalogue et franchit les mêmes points de contrôle.
648 résultats · Cybersecurity · Compétences
Search approved knowledge — Vulnerability Analyst, Cybersecurity
Search approved knowledge for Vulnerability Analyst teams in Cybersecurity, delivered by the Q&A Assistant pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a grounded response — Vulnerability Analyst, Cybersecurity
Draft a grounded response for Vulnerability Analyst teams in Cybersecurity, delivered by the Q&A Assistant pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review-ready answer — Vulnerability Analyst, Cybersecurity
Prepare a review-ready answer for Vulnerability Analyst teams in Cybersecurity, delivered by the Q&A Assistant pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft from supplied context — Vulnerability Analyst, Cybersecurity
Draft from supplied context for Vulnerability Analyst teams in Cybersecurity, delivered by the Drafting & Generation pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Follow configured behavior guidance — Vulnerability Analyst, Cybersecurity
Follow configured behavior guidance for Vulnerability Analyst teams in Cybersecurity, delivered by the Drafting & Generation pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare copy for revision — Vulnerability Analyst, Cybersecurity
Prepare copy for revision for Vulnerability Analyst teams in Cybersecurity, delivered by the Drafting & Generation pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize a supplied record — Vulnerability Analyst, Cybersecurity
Summarize a supplied record for Vulnerability Analyst teams in Cybersecurity, delivered by the Record Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess possible risk — Vulnerability Analyst, Cybersecurity
Assess possible risk for Vulnerability Analyst teams in Cybersecurity, delivered by the Record Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Flag items for human review — Vulnerability Analyst, Cybersecurity
Flag items for human review for Vulnerability Analyst teams in Cybersecurity, delivered by the Record Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run a parameterized read query — Vulnerability Analyst, Cybersecurity
Run a parameterized read query for Vulnerability Analyst teams in Cybersecurity, delivered by the Data Query & Summary pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize returned records — Vulnerability Analyst, Cybersecurity
Summarize returned records for Vulnerability Analyst teams in Cybersecurity, delivered by the Data Query & Summary pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a result-set overview — Vulnerability Analyst, Cybersecurity
Prepare a result-set overview for Vulnerability Analyst teams in Cybersecurity, delivered by the Data Query & Summary pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Check supplied context against policy — Vulnerability Analyst, Cybersecurity
Check supplied context against policy for Vulnerability Analyst teams in Cybersecurity, delivered by the Compliance Checker pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues — Vulnerability Analyst, Cybersecurity
Surface potential policy issues for Vulnerability Analyst teams in Cybersecurity, delivered by the Compliance Checker pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items — Vulnerability Analyst, Cybersecurity
Recommend review items for Vulnerability Analyst teams in Cybersecurity, delivered by the Compliance Checker pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context — Vulnerability Analyst, Cybersecurity
Assess supplied risk context for Vulnerability Analyst teams in Cybersecurity, delivered by the Risk Assessment pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers — Vulnerability Analyst, Cybersecurity
Explain assessment drivers for Vulnerability Analyst teams in Cybersecurity, delivered by the Risk Assessment pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review — Vulnerability Analyst, Cybersecurity
Recommend human review for Vulnerability Analyst teams in Cybersecurity, delivered by the Risk Assessment pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data — Vulnerability Analyst, Cybersecurity
Query supplied record data for Vulnerability Analyst teams in Cybersecurity, delivered by the Reconciliation Brief pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies — Vulnerability Analyst, Cybersecurity
Summarize potential discrepancies for Vulnerability Analyst teams in Cybersecurity, delivered by the Reconciliation Brief pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief — Vulnerability Analyst, Cybersecurity
Prepare a reconciliation brief for Vulnerability Analyst teams in Cybersecurity, delivered by the Reconciliation Brief pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception — Vulnerability Analyst, Cybersecurity
Assess a supplied exception for Vulnerability Analyst teams in Cybersecurity, delivered by the Exception Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment — Vulnerability Analyst, Cybersecurity
Summarize the assessment for Vulnerability Analyst teams in Cybersecurity, delivered by the Exception Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review — Vulnerability Analyst, Cybersecurity
Recommend follow-up review for Vulnerability Analyst teams in Cybersecurity, delivered by the Exception Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
L'installation est la partie facile. La gouvernance vient avec.
Les agents de la bibliothèque ne sont pas des scripts — ce sont des identités gouvernées. En installer un l'enregistre avec un propriétaire, un budget, des modèles et des actions autorisés, et une place dans le registre d'audit.
Choisissez dans le catalogue
Filtrez par secteur et par rôle ; chaque élément indique les systèmes auxquels il se connecte et les compétences qu'il invoque.
Reliez-le à votre stack
Connecteurs, serveurs MCP et imports OpenAPI — cadrés par des listes d'autorisation et le DLP au niveau de la passerelle.
Chaque exécution passe les verrous
Identité, budget, garde-fous, registre, Control Tower, exécution, garde-fou de sortie — puis un reçu signé dans le Trust Ledger. Sur toutes les formules.
Vous ne trouvez pas la compétence qu'il vous faut ?
Le générateur visuel de compétences livre de nouvelles compétences sans code — ou dites-nous ce qui manque et nous vous orienterons vers le modèle gouverné le plus proche.