Governance refers to Data Governance in MDM.
What is Governance?
...
Governance... | |
---|---|
references | where the Master Data is stored |
provides | visibility to data between zones and adaptors |
contains |
|
ACLs and ACL Chains
ACLs are a key component of YOUnite and are different from permissions in that they control where data flows through the system. Permissions control who can manage zones, users, groups, permissions, and roles.
An ACL chain can be thought of as a series (chain) of policies (ACLs) that can be applied to a data event that occurs in the MDM ecosystem.
...
Operation ACLs are not part of zone data governance but should be mentioned briefly here. By default, the DGS has permission to modify ACLs to . Operational ACLs set policies that set forth for a given data domain version:
- What zone can or can't POST or DELETE data records (DRs)
...
TODO: Add a POST/DELETE chart
ACLs Illustrated
TODO - Survey examples
...
- .
- What adaptors or can't POST or DELETE data records (DRs).
There is a single system-wide chain for Operational ACLs that is controlled by the DGS. By default all zones and adaptors can POST and DELETE data records but POST and DELETE polices for data records can be controlled by the DGS.
Operational ACL policies can be on the following:
Entity | Description |
---|---|
Domain Version | The domain version an operational ACL applies to. |
Source Zone | The zone that is allowed to or, restricted from POSTing a data record (DR). |
Source Adaptor | The adaptor that is allowed to or, restricted from POSTing a data record (DR). |
Allow POST / Restrict POST | Allow or restrict the source zone or adaptor from creating a data record for the given domain version. |
Allow DELETE / Restrict DELETE | Allow or restrict the source zone or adaptor from deleting a data record for the given domain version. |
ACLs Illustrated
A very simple example it illustrate this point:
- There are four three zones: ZoneW, ZoneX, ZoneY and ZoneZ each with only one adaptorZone-X, Zone-Y and Zone-Z each with two adaptors. All adaptors are capable of storing/retrieving data entries for the "Customer" domain
- ZoneW Zone-X has the following outbound ACL chain
- ALLOW all outbound data events from to flow through to ZoneY RESTRICT all outbound data events from flowing to all zonesOutbound ACL Chain
Source Zone | Destination Zone | Destination Adaptor | Domain Version | Policy | |
---|---|---|---|---|---|
1 | Zone-X | Zone-Y | ALL | ALL | ALLOW ALL |
2 | Zone-X | ALL | ALL | ALL | RESTRICT ALL |
ALL = GET, PUT, POST, DELETE
- A Customer PUT data event is raised on adaptor1 in
...
- Zone-X
- YOUnite can see that the adaptors in
...
- ZoneY and ZoneZ are all capable of consuming this data event
- YOUnite attempts to route the data event to
...
- Zone-Y
- YOUnite inspects
- Zone-Y
...
- Zone-X's outbound ACL chain and gets a match on the first ACL in the chain and routes the event to the
...
- two adaptors in Zone-Y
- YOUnite attempts to route the data event to
...
- Zone-Z
- The first ACL does not match but the second does restricting the event, so the data event is NOT routed to
- Zone-Z
...
TODO: Illustrate this
Examples worth mentioning:
Outbound ACL entry that includes domain properties:
- Need to include "allow" PUT and/or POST for them to take effect.
- The domain properties are a list of properties that should be restricted from flowing outbound
- The domain properties are ignored when "restrict" (e.g. restrict PUT or POST) is used since restrict is applied to the entire data event.
As mentioned above, governance provides visibility to data between zones and adaptors. This is typically managed by the ZDS, implemented with Access Control Lists (ACLs). ACLs are a key component of YOUnite. ACLs are different from permissions in that they control access to data. Permissions control who can manage zones, users, groups, permissions, and roles.
ACLs control both:
- Permissions on outbound data
- Controls on what inbound data a zone or adaptor should receive
TODO: Redraw and move to the top and re-use down here
For example, if an update (PUT or PATCH) operation is performed on data under YOUnite control, ACLs would control:
- What zones and adaptors would have visibility to the change (outbound ACLs)
- Which zones and adaptors receive (or reject) the change (inbound ACLs) e.g. a zone may be granted ACLs to a change but the ZDS for the zone may choose not to accept it.
Example Outbound ACLs for GET
These example ACLs are combined to create the effective outbound governance for a zone. DR-XXX represents a specific data record:
...
After applying all of the above, the end result is:
- ZoneX gets nothing
- Zone Y is restricted from seeing the two DRs listed above
- Student.feeWaiver on AdaptorB is not shared with any other zone
- Student.ssn is never shared with another zone (for all adaptors in the outbound zone)
Out-bound data permission is controlled at various levels. See an example of the data access, below.
...
1
...
- At the highest prioirty level (Priority 1), Zone[1] can shut off all outbound data record changes to Zone[2]. At the lowest priority level (Prioirty 5), Zone[1] can shut off sharing a single attribute on a single adaptor (that it owns) to Zone[2].
- Sharing precedence is based on the priority e.g. If Zone[1] has turned off access to Zone[2] (Priority 1), then all other sharing actions are null.
- Permissions for each element are based on REST operations GET, PATCH, POST and DELETE. An additional operation is added for PUSH, where a zone allows another zone to receive real-time changes. However, it may be determined that GET will include PUSH.
...
- Zone-Z
Following is more involved example using the zones and adaptors from above. ACLs are evaluated from first to last, the first match is applied to an incoming data event:
Source Zone | Source Adaptor | Destination Zone | Destination Adaptor | Domain Version | Data Records | Policy | Notes | |
---|---|---|---|---|---|---|---|---|
1 | Zone-X | ALL | Zone-Y | ALL | ALL | ALL | RESTRICT ALL | Restricts all outbound data events to Zone-Y |
2 | Zone-X | ALL | Zone-Y | Adaptor1 | ALL | ALL | RESTRICT ALL | This ACL is useless since ACL #1 already restrict all events to Zone-Y |
3 | Zone-X | ALL | Zone-Z | ALL | Customer v1 | DR-123, DR-456 | RESTRICT ALL | Restricts the data records (DR-123 and DR-456) from going to Zone-Z. |
4 | Zone-X | Adaptor2 | ALL | ALL | ALL | ALL | RESTRICT ALL | Restricts data events from flowing out of Zone-X's adaptor2 to all zones. |
5 | Zone-X | ALL | ALL | ALL | Customer v1 | Customer.ssn | RESTRICT ALL | Restricts a customer's SSN from flowing out of of Zone-X. |
6 | Zone-X | ALL | ALL | ALL | ALL | ALL | ALLOW ALL | Allow everything else out i.e. if a data event can be delivered to many adaptors in the YOUnite ecosystem it will be delivered to all adaptors except for the restrictions placed by the above ACLs. ALLOW ALL is the default so in reality, this ACL is unnecessary. |
ALL = GET, PUT, POST, DELETE
After applying all of the above, the end result is:
- Zone-Y gets nothing
- Zone-Z is restricted from seeing the two DRs listed above
- No data from Zone-X's Adaptor2 flows to any zones or adaptors
- Zone-X never shares the Customer version 1 Domain property Customer.ssn (for all adaptors in the outbound zones)
Complete ACL Data Flow Illustration
The image below represents an example of MDM domain-related permissions and operational, outbound, and inbound ACLs (traveling left to right). Additional text below the image describes the process in addition to the embedded in-image text.
TODO: Simplify this
the components involved as a data event is detected at an adaptor and flows through the YOUnite ecosystem.
- On the diagram's left side is a source zone’s single Source Adaptor (abcd-1234) that sends data changes (data records) in its domain(s) to the router.Note: A zone can have many adaptorsZone-X, Adaptor 1) detects a data event in the source system (ERP) and sends a data event (data record for a given domain version) to the router.
- The data records record sent from the source adaptor to the router have Operational ACL applied to them. Operational ACL limits which data operations are allowed (create/delete YOUnite Data Records) from the source zone’s adaptor(s) and adaptor domain(s) and are defined by the zone's DGS.
- Next, the data records from the source zone’s domains/adaptors are linked to YOUnite Data Records to avoid data record duplication.
- Note: The data records published by the source adaptor could be updates, deletes, or new records.
- Outbound ACLs then get applied to the source adaptor’s data recordsrecord (Zone-X, Adaptor 1). The Outbound ACLs are defined by the source zone’s ZDS and define what data the Zone can send out (i.e .restricting data, or elements of data, of certain domains from flowing out of certain adaptors in the zone to other zones).
- After Outbound ACLs are applied the data records are published to the YOUnite Data Hub and subscribing/desitnation zones and their adaptors (on the diagram's right side) are notified of the updated data.
- Any destination zone that has subscribed to data records from the source zone has Destination zones have Inbound ACLs in place to define which data operations are allowed in the from source zone zones and its their adaptor(s). Inbound ACL is defined by the destination zone’s ZDS. Any data or operations that are configured to be ignored restricted are filtered out. The Destination Adaptor (zyxw-9876) in the image above is shown receiving data records and/or operations it has subscribed to, as filtered by its zone’s Inbound ACL
- After Outbound ACLs are applied the data records are published to the YOUnite Data Hub Router and subscribing/desitnation zones and their adaptors (on the diagram's right side) are notified of the updated data.