Page Comparison

Governance refers to Data Governance in MDM.

TODO Mark

ACLs are defined similarly to firewall rules where rules are put in on inbound and outbound chains for a given zone.

ACLs can allow or restrict data flow.

Care must be taken to order the ACLs on a chain properly since the first ACL match is applied to a data event.

I very simple example it illustrate this point:

• There are four zones: ZoneW, ZoneX, ZoneY and ZoneZ each with only one adaptor. All adaptors are capable of storing/retrieving data entries for the "Customer" domain
• ZoneW has the following outbound ACL chain
  1. ALLOW all outbound data events from to flow through to ZoneY
  2. RESTRICT all outbound data events from flowing to all zones
• A Customer PUT data event is raised on adaptor1 in ZoneW
• YOUnite can see that the adaptors in ZoneX, ZoneY and ZoneZ are all capable of consuming this data event
  • YOUnite attempts to route the data event to ZoneX
    • YOUnite inspects ZoneW's outbound ACL chain and gets a match on the first ACL in the chain and routes the  event to the adaptor in ZoneX
  • YOUnite attempts to route the data event to ZoneY
    • The first ACL does not match but the second does restricting the event, so the data event is NOT routed to ZoneY
  •  ZoneZ experiences the same fate as ZoneY

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.

What is Governance?

Governance describes the act of managing data access (i.e. who accesses certain data sets based on role, application, etc.).

Governance: InboundAclEntries and OutboundAclEntries

...

• 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 adaptors.
• The data records sent from the source adaptor to the router have Operational ACL applied to them. Operational ACL limits which data operations are allowed 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 records. 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 Inbound ACLs in place to define which data operations are allowed in the source zone and its adaptor(s). Inbound ACL is defined by the destination zone’s ZDS. Any data or operations that are configured to be ignored 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.

...

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 data records (DRs) to zone users and adaptors to create new DRs. Operational ACLs control operations to the underlying DRs are granted by the DGS to Zone Users and Adaptors; typically the ZDSs.