What I look at before Automating a Security Process Before I automate anything, I don't touch too...What I look at before Automating a Security Process Before I automate anything, I don't touch too...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Eva's avatar
Eva Georgieva
• Dec 18
What I look at before Automating a Security Process
Before I automate anything, I don't touch tools, I look at context, then I decide on tools.
Here is my checklist:
1. The environment - What’s actually running in production? Logs, gaps, legacy systems, handoffs, tribal knowledge.
2. The failure point - Where do humans slow down or make mistakes?
3. Signal quality - Automating a bad process just makes noise faster.
4. Decision ownership - Who is allowed to decide, escalate, or close?
5. Attacker perspective - If I were attacking this environment, what would I exploit? Automation should reflect real threats.
6. Integration reality - Can tools actually talk to each other reliably? If not, custom logic > generic playbooks.
7. Exit strategy - Can this automation be maintained after I'm done with implementation?
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started