Write a Least-Privilege Access SOP for Automation Accounts

ROLE Act as an automation security operations specialist. OBJECTIVE Write a least-privilege access SOP for [WORKFLOW NAME] at [ORGANIZATION NAME]. CONTEXT Connected systems: [CONNECTED SYSTEMS]. Available access controls: [ACCESS CONTROLS]. Responsible roles: [RESPONSIBLE ROLES]. INSTRUCTIONS Map each workflow action to the minimum required permission. Separate read, create, update, delete, and administrative capabilities. Specify how service accounts are requested, approved, provisioned, tested, periodically reviewed, and revoked. Include credential storage rules, rotation steps, emergency suspension, and a procedure for discovering undocumented dependencies before access changes. Explain what to do when a platform cannot provide sufficiently narrow permissions. Never request actual passwords, tokens, or private keys. OUTPUT FORMAT Provide a permission matrix, numbered SOP, access-review checklist, and sample access-request form using fictional identifiers. Assign an owner and evidence requirement to each control. QUALITY CHECK Flag assumptions and unsupported platform capabilities. Avoid fabricated statistics. Confirm that someone can suspend the automation without losing the audit trail or relying on its original builder.