Translating XACML to Rego
Congrats if you know both of those key words. You’re in rare company.
Perhaps you are in an organization that uses XACML for all of your access control. And perhaps you’d like to switch to something else (Rego) for access control, but re-writing all of that XACML is way more cost-prohibitive and risky than you would like.
If so, we may have good news for you. PACLabs is pleased to announce Xackalope, our proprietary tool / service that faithfully translates XACML into Rego. The new Rego will have the exact same behavior as the XACML, because it replicates the XACML specification.
It is available in three form factors:
As a java war file, which can be installed into your existing infrastructure, with support for HTTPS, vault-stored credentials, access control and a variety of input and output APIs
As a container which hosts said War file, for an easier installation
As a service, where we host the container on your behalf.
Pricing is reasonable and flexible. If you want to convert your XACML to Rego and then adopt Rego from that point forward, you don’t need a long-term commitment with us. If you’d like to keep authoring XACML, but take advantage of Open Policy Agent, etc for implementation, you can choose a low-cost ongoing license to convert new XACML as it is authored.
If you need assistance in designing and integrating an OPA/Rego-based access control solution, we can help here as well. And of course, we offer post-installation support at a variety of tiers to support your needs and budget.
If you’d like to know more, please contact us at: johnbr@paclabs.io