lolcreds

Public credential defaults and exposure patterns for authorized security testing.

PagerDuty

PagerDutymonitoring3 credentials

Credentials3 documented
01

REST API Key

pagerduty / rest-api-key

PagerDuty REST API keys authenticate automation against the PagerDuty REST API. PagerDuty documents General Access and User Token REST API keys, and states both types are 20-character strings.

user definedsecretAPI key

Looks like

example
example

PagerDuty REST API keys are documented as 20-character strings; use with PagerDuty context

abcdefghijklmnopqrst

Location

http header
Authorization

Token authentication header used for PagerDuty REST API requests

environment
PAGERDUTY_API_KEY, PD_API_KEY, PAGERDUTY_TOKEN, PAGERDUTY_API_TOKEN
config file
pagerduty.json, pagerduty.yaml, pd.yml, terraform.tfvars, provider.tf

Terraform provider config, automation .env files, runbooks, and deployment manifests; Removed generic/common scanner surface path(s) from product template: .env

secret store

CI/CD variables, cloud secret managers, and incident automation secrets

source code

incident automation scripts, Terraform modules, tests, and committed examples

logs

API client traces, Terraform logs, and CI output

Notes

REST API keys do not work with PagerDuty Events API calls. User token keys act with the creating user's permissions.

02

Events API Integration / Routing Key

pagerduty / events-routing-key

PagerDuty Events API integrations use routing keys to route events to a service or event orchestration. PagerDuty distinguishes Events API keys from REST API keys in its API access key documentation.

generated on installsecretAPI key

Looks like

example
example

PagerDuty Events API integration/routing keys are commonly 32 hex characters

0123456789abcdef0123456789abcdef

Location

environment
PAGERDUTY_ROUTING_KEY, PD_ROUTING_KEY, PAGERDUTY_INTEGRATION_KEY
config file
pagerduty.json, pagerduty.yaml, services.yml, event-rules.yml, terraform.tfvars

monitoring alert configs, IaC, .env files, and deployment manifests; Removed generic/common scanner surface path(s) from product template: .env

secret store

monitoring platform secrets, CI/CD variables, and cloud secret managers

source code

alerting scripts, examples, and committed service integrations

logs

event submission logs and incident automation traces

http response

integration creation responses containing routing or integration keys

Notes

A leaked routing key can trigger or manipulate events for the associated service or orchestration but does not grant REST API access.

03

OAuth Access Token

pagerduty / oauth-access-token

PagerDuty supports OAuth access for apps and API integrations. OAuth access tokens authenticate API calls with delegated scopes instead of a static REST API key.

generated on installsecrettoken

Location

http header
Authorization

Bearer OAuth access token used for PagerDuty API calls

http response

OAuth token endpoint responses containing access_token and refresh_token

database

app installation token stores

config file
pagerduty-oauth.json, oauth-token.json, pd.yml

OAuth example config and integration settings

secret store

encrypted app secrets and cloud secret managers

logs

OAuth callback logs and token exchange traces

Notes

OAuth token blast radius depends on app scopes, installation, and the user or account context granting access.

Scope

Authorized use

LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.