VIDEO TRANSCRIPT
Hi, everyone. My name is Rob. I'm head of product and customer success for Oobi, and I have the distinct pleasure of ensuring the delivery of product value for our clients and providing support and enablement along the way.
I oversee the product training and delivery for our technical teams and work directly with product development for feature refinement.
Now I promised a riveting demo, with minimal slide wear, but wanted to just set the scene of why we're all here and that's to, because we're contending with what we affectionately call the macro problem.
And the macro problem is a practice which, if not controlled, can represent a real security risk.
Malicious actors can embed malware to macro or PowerShell code commonly used in BAU operations.
We face a threat where security can be bypassed and access can be gained. So it's a genuine concern which is enshrined in numerous regulatory frameworks such as ones from ACSC and PPSF.
Traditionally, there are three ways you can address the macro problem as an organization.
We have door number one, option one. You can block all the macros.
This would block the risk associated with malware, but would create additional risks and issues. We would see productivity impacts. Our users may be forced to find workarounds to circumvent controls.
Or worse, we might end up with a frustrated workforce, which has various flow and effects. So option one, far from ideal.
We have option two. We can allow all the macros that do nothing and react sort of approach. So while this would have no immediate productivity impacts, we're exposing ourselves to significant potential risk in reputation, time, and money loss associated with incident response, not to mention noncompliance with the regulatory frameworks. So, again, option two, not ideal either.
Door number three, you can manually assess macro code, per macro each time, allowing users to run macros, but after much delay. Your entire business becomes dependent on your IT teams to enable BAU efficiency with macros, And this demands a highly advanced cybersecurity skill set to assess the code, slows down the users, it increases the cost from multiple teams, and reduces the efficiency benefit from the macros.
So none of these options provide a low effort and high value outcome.
So let's look behind door or option number four, which enter the answer to the macro problem, MacroSign.
MacroSign provides automatic code assessment and digital signing of macro and PowerShell code, completely hosted from within your IT environment.
It makes it easy to achieve regulatory compliance and takes the heavy lifting out of uplifting your essential eight maturity level.
It's the most efficient approach to securing macros in bulk for your teams and is provided through an easy to use self-service portal so enough slide where how about that demo?