When it comes to securing access to services and data, we see many different use cases and, with that, the enforcement of authorization rules at different layers in the IT stack. This spans all the way from the Web/Presentation tier down to the data tier as illustrated in Figure 1. Enforcing
It’s hard to believe, but it’s already been 10 years since I had the honor to host the first ever XACML interoperability demonstration at Burton Group’s Catalyst conference in June of 2007. We had a long tradition of hosting interoperability demonstrations, but they were typically associated
Splunk is a Security Information and Event Management (SIEM) tool that can be used to aggregate and analyze security logs. Axiomatics Policy Server (APS) can be configured to generate audit logs that monitor who logs in to the Axiomatics Services Manager (ASM) and who does what within the ASM.
While it is predicted that “by 2020, 70% of enterprises will use Attribute-Based Access Control (ABAC) to protect critical assets” (Gartner), a lot of confusion still lingers around what exactly an organization can expect to get out of ABAC, or Dynamic Authorization. A quick
If you missed part 1 or 2 of our GDPR blog series, you can find them here: Part 1: A GDPR Primer: What You Need to Know Part 2: GDPR: A Driver for Digitalization In this post, we will outline a practical approach for achieving GDPR compliance with the help of technology, specifically
Attribute-based access control (ABAC) lets us define fine-grained authorization policies that typically take into account user attributes and resource attributes. Sometimes we may need time to express authorization constraints. For example: Only a supervisor can view the medical record of a
