Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Account provisioning is the process by which user accounts are created, modified, and managed by administrators or automated systems. This test evaluates the security of the provisioning workflow, including how accounts are created, what privileges are assigned, and whether proper authorization is required. Weaknesses in provisioning can lead to unauthorized account creation, privilege escalation, and insider threats.
What to Check
Provisioning Security Controls
Authorization required for account creation
Approval workflows exist
Audit logging of provisioning actions
Principle of least privilege applied
Separation of duties enforced
Temporary/service account management
Account Lifecycle Stages
Stage
Security Consideration
Creation
Who can create accounts? Authorization required?
Modification
Who can change roles/permissions?
Suspension
Process for disabling accounts
Deletion
Complete removal of access and data
Review
Regular access reviews conducted?
How to Test
Step 1: Identify Provisioning Endpoints
# Admin user creation endpoints
curl -s -H "Authorization: Bearer $ADMIN_TOKEN" \
"https://target.com/api/admin/users" -X GET
# Check for provisioning API
curl -s -H "Authorization: Bearer $ADMIN_TOKEN" \
"https://target.com/api/admin/provision" -X GET
# Look for bulk user creation
curl -s -H "Authorization: Bearer " \
-X GET
curl -s -H \
-X GET
$ADMIN_TOKEN
"https://target.com/api/admin/users/bulk"
# Self-service provisioning
"Authorization: Bearer $USER_TOKEN"
"https://target.com/api/users/invite"
Step 2: Test Authorization for Provisioning
# Try creating user with non-admin token
curl -s -X POST "https://target.com/api/admin/users" \
-H "Authorization: Bearer $USER_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"username": "unauthorized_user",
"email": "unauthorized@test.com",
"password": "TestPass123!",
"role": "user"
}'# Try without any authentication
curl -s -X POST "https://target.com/api/admin/users" \
-H "Content-Type: application/json" \
-d '{
"username": "noauth_user",
"email": "noauth@test.com",
"password": "TestPass123!"
}'
Step 3: Test Privilege Escalation During Provisioning