- 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.
864 résultats · Cybersecurity
Check supplied context against policy — Detection Engineer, Cybersecurity
Check supplied context against policy for Detection Engineer 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 — Detection Engineer, Cybersecurity
Surface potential policy issues for Detection Engineer 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 — Detection Engineer, Cybersecurity
Recommend review items for Detection Engineer 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 — Detection Engineer, Cybersecurity
Assess supplied risk context for Detection Engineer 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 — Detection Engineer, Cybersecurity
Explain assessment drivers for Detection Engineer 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 — Detection Engineer, Cybersecurity
Recommend human review for Detection Engineer 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 — Detection Engineer, Cybersecurity
Query supplied record data for Detection Engineer 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 — Detection Engineer, Cybersecurity
Summarize potential discrepancies for Detection Engineer 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 — Detection Engineer, Cybersecurity
Prepare a reconciliation brief for Detection Engineer 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 — Detection Engineer, Cybersecurity
Assess a supplied exception for Detection Engineer 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 — Detection Engineer, Cybersecurity
Summarize the assessment for Detection Engineer 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 — Detection Engineer, Cybersecurity
Recommend follow-up review for Detection Engineer 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.
Run an on-demand read query — Detection Engineer, Cybersecurity
Run an on-demand read query for Detection Engineer teams in Cybersecurity, delivered by the On-demand Reporting & Insights 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 query results — Detection Engineer, Cybersecurity
Summarize query results for Detection Engineer teams in Cybersecurity, delivered by the On-demand Reporting & Insights 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.
Highlight supplied exceptions — Detection Engineer, Cybersecurity
Highlight supplied exceptions for Detection Engineer teams in Cybersecurity, delivered by the On-demand Reporting & Insights 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 context — Detection Engineer, Cybersecurity
Assess supplied context for Detection Engineer teams in Cybersecurity, delivered by the Decision Support 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 recommended response — Detection Engineer, Cybersecurity
Draft a recommended response for Detection Engineer teams in Cybersecurity, delivered by the Decision Support 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 rationale for review — Detection Engineer, Cybersecurity
Prepare rationale for review for Detection Engineer teams in Cybersecurity, delivered by the Decision Support 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 supplied work — Detection Engineer, Cybersecurity
Summarize supplied work for Detection Engineer teams in Cybersecurity, delivered by the Routing Advisor 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 priority and risk — Detection Engineer, Cybersecurity
Assess priority and risk for Detection Engineer teams in Cybersecurity, delivered by the Routing Advisor 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 a routing decision — Detection Engineer, Cybersecurity
Recommend a routing decision for Detection Engineer teams in Cybersecurity, delivered by the Routing Advisor 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 historical data — Detection Engineer, Cybersecurity
Query supplied historical data for Detection Engineer teams in Cybersecurity, delivered by the Trend Briefing 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 observed trends — Detection Engineer, Cybersecurity
Summarize observed trends for Detection Engineer teams in Cybersecurity, delivered by the Trend Briefing 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 questions for forecast review — Detection Engineer, Cybersecurity
Prepare questions for forecast review for Detection Engineer teams in Cybersecurity, delivered by the Trend Briefing 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.