It makes sense to grant access to the agent folder only for DevOps administrators and the user identity running the agent process. Therefore, it is safer to carefully consider access granted to the agent machine itself, and the agent folders which contain sensitive files, such as logs and artifacts. The user generating the credentials (and other agent-related files) is different than the user that needs to read them. It is a best practice to have the identity running the agent be different from the identity with permissions to connect the agent to the pool. Therefore, it is important to consider the threat model surrounding each individual usage of Pipelines Agents to perform work, and decide what are the minimum permissions could be granted to the user running the agent, to the machine where the agent runs, to the users who have write access to the Pipeline definition, the git repos where the yaml is stored, or the group of users who control access to the pool for new pipelines. It inherently could be a target for Remote Code Execution (RCE) attacks. The Azure Pipelines agent is a software product designed to execute code it downloads from external sources. The folders controlled by the agent should be restricted to as few users as possible and they contain secrets that could be decrypted or exfiltrated. The user configuring the agent needs pool admin permissions, but the user running the agent does not. Prepare permissions Information security for self-hosted agents On the other hand, the bulk of the Azure DevOps code is built by 24-core server class machines It's not possible to make a general recommendation that will apply to everyone.Īs a point of reference, the Azure DevOps team builds the hosted agents code using pipelines that utilize hosted agents. The hardware specs for your agents will vary with your needs, team size, etc. You should run agent setup manually the first time.Īfter you get a feel for how agents work, or if you want to automate setting up many agents, consider using unattended config. Recommended - Visual Studio build tools (2015 or higher).
#Talisman online private server website install
Subversion - If you're building from a Subversion repo, you must install the Subversion client on the machine.The agent software installs its own version of.Make sure your machine has these prerequisites: But if you'd like some more background about what they do and how they work, see Azure Pipelines agents.
If you already know what an agent is and how it works, feel free to jump right in to the following sections. If you're using Azure DevOps Services and a Microsoft-hosted agent meets your needs, you can skip setting up a self-hosted Windows agent.
#Talisman online private server website how to
This article describes how to configure a self-hosted agent.
0 kommentar(er)
