Alex on the Azure Practice call - LBG not understanding the potential behind using Policy to not just Deny…
Simple No-Code Solution
More Complex
Some ideas - no filters :P
emulating the bank setup for where we can access Policy generated event logs, we mirror the setup and ensure we capture events to a compatible input source for flows
if we cannot access data directly, we can replicate the behaviour in Jan’s POC where he leverages policy compliance events to log - so either use as is deliver the simple No-Code solution
a DefaultDeny policy opens a great conversation in my mind - as SecOps ppl do tend to forget how transferable and still-relevant their skills aer (secops people I finds have always been the hardest converts due to alot of “automate me out” concerns - i mean they are the last bastion to appreciate what we want to achieve right here :P
I am more than happy to share my well-used conversion process if you’re interested…
SecOps and the general function deal with Absolutes
these absolutes are yes or no
they are risk categorisation
they are fact verification
The list does go on - but in general they get something, they pick a set if rules that matches that something (using another set of rules) and they chug through that list to verify or categorise and approve
That my friends is pseudo-code; or specifically no-code.






