BeyondTrust Password Safe
Read scan credentials from BeyondTrust Password Safe through its public API, with a password request per scan that is checked in when the scan ends.
BeyondTrust Password Safe
Reference
pam://beyondtrust/<SystemName>/<AccountName>Example: pam://beyondtrust/web-prod-01/svc_dast.
How a read works
POST Auth/SignAppinwithAuthorization: PS-Auth key=<api_key>; runas=<run_as>;.GET ManagedAccounts?systemName=...&accountName=...finds the system and account ids.POST Requestsopens a release request forduration_minutes, withreasonas the request reason. If a request for that account is already open (409), it is reused.GET Credentials/<requestId>returns the password.- When the scan ends:
PUT Requests/<requestId>/Checkinfor every request the runner opened, thenPOST Auth/Signout.
A second read of the same account in one scan (a DAST re-login) reuses the open request.
What the BeyondTrust administrator prepares
- An API registration for Safeguard, with authentication rules limited to the runner's address, and its API key.
- A run-as user that may request the scan managed accounts, with no approval step for this user.
- The scan accounts managed by Password Safe, with a release duration that covers a scan.
Runner configuration
providers:
- type: beyondtrust
url: https://pws.example.internal/BeyondTrust/api/public/v3
api_key: file:///etc/safeguard/bt-api-key
run_as: svc-safeguard
reason: Safeguard scan
duration_minutes: 120
ca_cert: /etc/safeguard/internal-root-ca.pemIf a scan stops before it ends cleanly (the machine loses power), the request is not checked in and stays open until its duration ends.
HashiCorp Vault
Read scan credentials from HashiCorp Vault KV v1 or v2 and dynamic secrets engines, with token, AppRole or Kubernetes sign-in, and lease revocation at scan end.
Delinea Secret Server
Read scan credentials from Delinea Secret Server with an OAuth2 sign-in and the secret field endpoint, using the delinea provider type in the runner's provider file.