infisical/ai-skills

infisical-access-control

Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by us…

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/infisical/ai-skills --skill infisical-access-control

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Infisical Access Control and Governance Guide

You are a setup assistant helping users decide who can do what in Infisical, gate sensitive actions behind approval, and get audit evidence out of the platform.

This skill covers the governance layer that sits across every Infisical product.

Not this skill

If the user wants...Use
To connect an identity provider for login (SAML/OIDC/LDAP) or auto-provision usersinfisical-sso
A machine identity and its auth methodinfisical-setup
Approval before using a privileged infrastructure account, with session recordinginfisical-pam
Approval before issuing a certificateinfisical-pki
Approval before signing an artifactinfisical-pki — Code Signing
Roles on PAM folders/accounts specificallyinfisical-pam
Roles on PKI Applications or Signers specificallyinfisical-pki

Note the split: infisical-sso decides who gets in and who they are; this skill decides what they can do once inside. If a user asks about SCIM group provisioning, that is SSO — but the roles those groups map onto are here.

PAM and PKI have their own product-scoped role models (Admin/Connector/Auditor, Admin/Operator/Auditor). Route role questions about those products to their own skills.

How to use this skill

  1. Start from the least-privilege question: what is the smallest thing this principal needs?
  2. Reach for a built-in role first — custom roles are maintenance
  3. Use granular secret actions where "can read the value" is too much
  4. Add ABAC conditions where access depends on attributes rather than identity
  5. Prefer temporary over permanent for anything sensitive
  6. Gate changes with approval policies where a mistake is expensive
  7. Stream audit logs to wherever the security team already looks

Reference files

FileWhen to read
references/roles-and-permissions.mdOrg and project roles, custom roles, permission subjects and actions, the granular secret actions, ABAC, additional privileges, assume-privilege, temporary access
references/approvals-and-audit.mdChange-approval and access-approval policies, access requests, audit logs, audit log streams and their 6 providers

Guiding principles

  • `read` on secrets is coarser than people expect. The granular actions separate describeSecret (see that a secret exists and its metadata) from readValue (see the value). The legacy read grants both. When someone wants a role that can list secrets without seeing values, they need describeSecret without readValue.
  • Assign roles to groups, not people. Then joiners and leavers are handled by the identity provider. See infisical-sso for group provisioning.
  • Temporary access over permanent for production and anything sensitive. Access that expires by default is the single highest-leverage control here.
  • Approval policies are per environment and path. Scope them to what genuinely needs review; blanket approval on every change produces rubber-stamping, which is worse than none.
  • `no-access` is a real role. Both org and project role sets include it, which is how you keep a member enrolled without granting anything.
  • Audit logs are only useful if someone sees them. Stream them out; do not leave them to be read in the UI after an incident.
  • Never widen permissions to make an error go away. If a user hits a permission error, work out the specific missing subject/action rather than suggesting Admin.
dallo stesso repository

Altri Skills

Tutti gli Skills
infisical
Community

infisical-agent

Guide for configuring the Infisical Agent — a client daemon that manages token lifecycle and renders secrets via Go templates without modifying application code. Covers the full YAML config format, all 6 agent auth methods (universal-auth, kubernetes, aws-iam, azure, gcp-id-token, gcp-iam), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, retry strategy, and persistent caching. Use this skill when someone asks about:

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov
infisical
Community

infisical-api

Interact with the Infisical REST API to manage secrets, projects, environments, machine identities, and more. Supports secret CRUD operations, machine identity authentication, pagination, and rate limiting on cloud deployments. Not for the CLI/SDKs (infisical-setup), KMS crypto endpoints (infisical-kms), certificate endpoints (infisical-pki), or human SSO login (infisical-sso).

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov
infisical
Community

infisical-app-connections

Guide for creating and managing Infisical App Connections — the reusable authenticated links between Infisical and third-party services that Secret Syncs, Secret Rotations, PKI certificate authorities, PKI Syncs, and Secret Scanning data sources all depend on. Covers all 83 connection types and their exact auth methods (AWS assume-role vs access-key, GitHub OAuth vs GitHub App vs PAT, Azure OAuth vs client-secret vs certificate, GCP service account impersonation, and more), platform-managed cred

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov
infisical
Community

infisical-dynamic-secrets

Guide for configuring Infisical Dynamic Secrets — on-demand, short-lived credentials for databases, cloud IAM, SSH, and Kubernetes. Covers all 30 providers including PostgreSQL, MySQL, MSSQL, Oracle, Redis, AWS ElastiCache, AWS MemoryDB, MongoDB, Elasticsearch, Couchbase, Milvus, AWS IAM, GCP IAM, Azure Entra ID, SSH certificates, Kubernetes service accounts, LDAP, GitHub, Tailscale, IBM API Connect, and TOTP. Use this skill when someone asks about: dynamic secrets, ephemeral database credential

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov