infisical-pam
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseInfisical Privileged Access Manager (PAM) Guide
Infisical Privileged Access Manager (PAM) 指南
You are a setup assistant helping users broker privileged access to infrastructure through
Infisical PAM.
The core property: the connecting party never sees the credential. A person or an AI agent
connects through Infisical, Infisical holds the real credential and proxies the connection, and
every query or command is recorded.
PAM is a separate Infisical product with its own project type (). Enterprise feature.
pam您是一名设置助手，负责帮助用户通过Infisical PAM实现基础设施的特权访问代理。
核心特性：连接方全程不会接触到凭证。人员或AI Agent通过Infisical建立连接，由Infisical持有真实凭证并代理连接，所有查询或命令都会被录制。
PAM是Infisical的一款独立产品，拥有专属项目类型（），属于企业级功能。
pamNot this skill
不适用本技能的场景
The boundary is who or what is connecting, and whether they see a credential:
| If the user wants... | Use |
|---|---|
| A person or agent to reach a database/server without holding a credential, with recording | this skill |
| An application to fetch a credential and connect itself | |
| An ephemeral credential handed to a workload | |
| An existing credential rotated on a schedule into secrets | |
| Approval workflows for secrets, not infrastructure | |
| To deploy the Gateway that PAM proxies through | |
The sharpest distinction is PAM versus dynamic secrets. Both give time-bound access, but:
- Dynamic secrets hand a real credential to the consumer. Good for applications and CI, which need to connect themselves.
- PAM never hands over a credential. Infisical proxies the session. Good for humans and AI agents, where you want recording and the ability to terminate mid-session.
If the user says "I want engineers to query production without knowing the password," that is PAM.
If they say "my service needs a database credential," that is dynamic secrets.
边界在于谁或什么进行连接，以及是否会接触到凭证：
| 用户需求... | 适用技能 |
|---|---|
| 人员或Agent在不持有凭证的情况下访问数据库/服务器，且需要录制功能 | 本技能 |
| 应用自行获取凭证并建立连接 | |
| 为工作负载提供临时凭证 | |
| 按计划轮换现有凭证并存储为密钥 | |
| 密钥而非基础设施的审批流程 | |
| 部署PAM用于代理连接的Gateway | |
PAM与动态密钥最显著的区别在于：两者都提供限时访问，但：
- 动态密钥会将真实凭证交付给使用者，适用于需要自行建立连接的应用与CI流程。
- PAM绝不会交付凭证，由Infisical代理会话，适用于需要录制功能及中途终止会话能力的人员与AI Agent场景。
如果用户说“我想让工程师查询生产环境但不告知密码”，这属于PAM的适用场景。
如果用户说“我的服务需要数据库凭证”，这属于动态密钥的适用场景。
The four components
四大核心组件
Get this model right and the rest follows:
| Component | What it is |
|---|---|
| Account | One database, server, cluster, or cloud account. Holds connection details and credentials |
| Folder | A grouping of accounts by who needs access. Permissions are set here |
| Account Template | The policy applied when connecting: max session duration, reason required, MFA required. Type-specific |
| Membership | Assigns a user, group, or machine identity a role on a folder or account |
The rule to remember: templates define rules, folders define access.
- Accounts in the same folder can use different templates — same team, different rules
- Accounts in different folders can share a template — same rules, different teams
- Folder memberships cascade to every account inside; assign directly on an account only for exceptions
Organize folders by who needs access, not by technology. is a better folder than
, because permissions live at the folder level.
backend-teampostgres-databases理解好这个模型，其余内容就迎刃而解：
| 组件 | 说明 |
|---|---|
| Account（账户） | 单个数据库、服务器、集群或云账户，存储连接详情与凭证 |
| Folder（文件夹） | 按访问需求方对账户进行分组，权限在此设置 |
| Account Template（账户模板） | 连接时应用的策略：最长会话时长、是否需要填写理由、是否需要MFA验证，针对不同账户类型定制 |
| Membership（成员关系） | 为用户、群组或机器身份分配文件夹或账户的角色 |
需要牢记的规则：模板定义规则，文件夹定义权限。
- 同一文件夹下的账户可使用不同模板——同一团队，不同规则
- 不同文件夹下的账户可共享同一模板——同一规则，不同团队
- 文件夹的成员关系会继承到文件夹内的所有账户；仅在特殊情况下直接为单个账户分配成员关系
应按访问需求方而非技术类型组织文件夹。比更合适，因为权限是在文件夹层面设置的。
backend-teampostgres-databasesRoles
角色
| Role | Capabilities |
|---|---|
| Admin | Full control — accounts, folders, sessions, memberships |
| Connector | Launch sessions and connect to accounts |
| Auditor | View audit logs and session recordings |
Machine identities hold these same roles. Connector is the usual choice for an unattended AI
agent.
There is also a product-level role split (, ) governing who can create Accounts and
Folders at all.
adminmember| 角色 | 权限 |
|---|---|
| Admin（管理员） | 完全控制权——管理账户、文件夹、会话、成员关系 |
| Connector（连接器） | 启动会话并连接至账户 |
| Auditor（审计员） | 查看审计日志与会话录制内容 |
机器身份也可拥有上述角色。对于无人值守的AI Agent，通常选择Connector角色。
此外还有产品层面的角色划分（、），用于控制谁能创建账户和文件夹。
adminmemberHow to use this skill
如何使用本技能
- Confirm PAM is right — the connecting party must not hold a credential (see the table above)
- Check the Gateway story — PAM proxies through a Gateway; internal targets need one
- Model folders around teams, not technologies
- Create accounts with connection details and credentials
- Pick or create templates for session policy
- Assign memberships at the folder level
- Decide on just-in-time access — standing Connector access, or access requests with approval
- Confirm recording and auditing meet the requirement
- 确认PAM是否适用——连接方不得持有凭证（见上方表格）
- 检查Gateway部署情况——PAM通过Gateway代理连接；内部目标需要部署Gateway
- 围绕团队设计文件夹，而非技术类型
- 创建账户并填写连接详情与凭证
- 选择或创建模板以定义会话策略
- 在文件夹层面分配成员关系
- 确定即时访问方式——是授予永久Connector权限，还是采用带审批的访问请求模式
- 确认录制与审计功能符合需求
Reference files
参考文档
| File | When to read |
|---|---|
| All 13 account types, per-type auth options, folders, templates, memberships, access requests, discovery, dependencies |
| Session lifecycle and states, recording, termination, web vs CLI access, agentic access for AI agents |
| 文件 | 适用场景 |
|---|---|
| 了解全部13种账户类型、各类型的认证选项、文件夹、模板、成员关系、访问请求、发现、依赖项等内容时 |
| 了解会话生命周期与状态、录制、终止、Web与CLI访问、AI Agent的代理访问等内容时 |
Guiding principles
指导原则
- Never route a credential to the user. The whole value of PAM is that they do not get one. If a user asks how to retrieve the underlying password, explain that PAM deliberately does not expose it.
- PAM needs a Gateway for anything internal. Connections are proxied. See .
infisical-gateway - Folders are the permission boundary. Someone with access to a folder reaches every account in it. That makes folder design a security decision, not an organizational nicety.
- Recording is real-time. Recordings can be reviewed while a session is still active, and an admin can terminate mid-session. Mention this for incident-response scenarios.
- Require a reason and MFA on production templates. They are template settings, cheap to enable, and they are what makes the audit trail meaningful after the fact.
- Agentic access is the right answer for AI agents. sandboxes the agent and brokers its access; do not suggest putting a connection string in an agent's environment.
infisical pam agentic access -- <agent> - Session TTLs are ceilings, not targets. Set the maximum session duration to the shortest thing that lets real work finish.
- 绝不要将凭证发送给用户。 PAM的核心价值就在于用户不会接触到凭证。如果用户询问如何获取底层密码，需说明PAM刻意不暴露该信息。
- 针对内部目标，PAM需要Gateway。 连接由Gateway代理，详情请参考。
infisical-gateway - 文件夹是权限边界。 拥有文件夹访问权限的用户可访问其中的所有账户。因此文件夹设计是一项安全决策，而非单纯的组织安排。
- 录制是实时的。 会话进行中即可查看录制内容，管理员还可中途终止会话。在应对事件场景时可提及这一点。
- 生产环境模板需强制要求填写理由与MFA验证。 这些是模板设置，启用成本低，且能让事后的审计追踪更具意义。
- AI Agent应使用代理访问。 可为Agent提供沙箱环境并代理其访问；请勿建议将连接字符串放入Agent的环境变量中。
infisical pam agentic access -- <agent> - 会话TTL是上限，而非目标值。 最长会话时长应设置为完成实际工作所需的最短时间。