<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Manoj Kukreja on Medium]]></title>
        <description><![CDATA[Stories by Manoj Kukreja on Medium]]></description>
        <link>https://medium.com/@mkukreja1?source=rss-4076fc16cb6a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IUHpXN1P5DaLIWjXsohPfA.jpeg</url>
            <title>Stories by Manoj Kukreja on Medium</title>
            <link>https://medium.com/@mkukreja1?source=rss-4076fc16cb6a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 09:47:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mkukreja1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Let’s talk about Data Governance — Dimension 4— Data Lineage Tracking Policies]]></title>
            <link>https://mkukreja1.medium.com/lets-talk-about-data-governance-dimension-4-data-lineage-tracking-policies-dbd85fdb08c7?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbd85fdb08c7</guid>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 20:52:43 GMT</pubDate>
            <atom:updated>2026-11-11T20:52:43.539Z</atom:updated>
            <content:encoded><![CDATA[<h4>From Creation to Consumption: Understanding Where Data Comes From, How It Changes, and Where It Goes</h4><p><strong>Data lineage</strong> is the practice of tracking the usage of data as it flows through systems — from where it’s created to where it’s consumed. It involves systematic documentation of data origins, flow, dependencies, transformations, and downstream consumption across systems throughout the data lifecycle. Data lineage policies enable control, trust, and governance over data in complex, distributed data ecosystems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*MkpHNe1VRpp6OXKubFRaYA.png" /><figcaption>Image by author — Dimension 4 — Data Lineage Tracking Policies</figcaption></figure><h3>Data Lineage Tracking Policies</h3><p>In modern, distributed data architectures, data lineage policies provide the foundation for control, trust, and effective governance. By making data flows transparent and traceable, lineage enables organizations to manage complexity, reduce risk, and scale analytics with confidence.</p><blockquote>Data Lineage refers to the ability to trace the full journey of data over time. Many compliance frameworks treat data lineage as concrete evidence of whether an organization has adhered to best practices for data usage.</blockquote><h3>Benefits of Tracking Data Lineage</h3><p>From both a technical and organizational standpoint, the value of data lineage policies is realized across several critical areas as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*uLiKJbXyZJwRxiRgcV_K8g.png" /><figcaption>Image by author: Benefits of data lineage policies</figcaption></figure><h4>Impact Analysis and Change Management</h4><p>In complex data architectures with tightly coupled and highly interdependent assets, the ability to proactively detect and remediate issues is critical. Data lineage enables:</p><ul><li><strong>Impact and risk assessment</strong> for pipeline, schema, or transformation changes by identifying all downstream dependencies prior to modification.</li><li><strong>Prevention of unintended downstream failures</strong> across reports, dashboards, APIs, and machine learning models.</li><li><strong>Reduced mean time to resolution (MTTR)</strong> by enabling precise upstream and downstream tracing to the originating source, process, or transformation.</li><li><strong>Accelerated root-cause analysis</strong>, eliminating reliance on blind or manual debugging across multiple systems.</li></ul><h4>Trust and Auditability</h4><p>Data lineage provides clear visibility into how data is sourced, transformed, and processed throughout its lifecycle. This visibility allows stakeholders to validate calculations, confirm business rules, and evaluate data completeness and accuracy. As a result, it strengthens confidence in dashboards, reports, and analytical outputs, while helping establish a trusted single source of truth for decision‑making.</p><p>In addition, regulatory and internal governance requirements frequently require well‑defined documentation of data provenance and transformation logic.</p><blockquote>Data lineage supports auditable traceability of sensitive and regulated data by clearly documenting its origins, transformations, and usage, thereby demonstrating compliance with organizational policies, industry standards, and regulatory obligations.</blockquote><h4>Resilience and scalability</h4><p>As data platforms scale in both size and architectural complexity, institutional knowledge of data flows, dependencies, and transformations becomes increasingly fragmented and difficult to maintain. Critical understanding of how data is produced and consumed often resides in undocumented pipelines, legacy code, or individual expertise, creating operational risk.</p><p>Data lineage systematically captures and externalizes this knowledge by formally documenting end-to-end data flows, transformation logic, and asset dependencies across systems. By reducing reliance on tribal or implicit expertise, lineage improves organizational resilience and continuity. New team members can onboard more quickly, cross-functional teams can collaborate more effectively, and knowledge transfer becomes repeatable and auditable.</p><blockquote>As teams, technologies, and platforms evolve, data lineage provides a durable, system-level record that supports operational stability, reduces single points of failure, and enables sustainable scaling of data engineering, analytics, and governance capabilities.</blockquote><h4>Ownership and accountability</h4><p>Data lineage plays a critical role in establishing and enforcing clear <strong>ownership and accountability</strong> across the data lifecycle. In complex, distributed data environments, data assets often span multiple systems, teams, and business domains, making it difficult to determine who is responsible for data quality, integrity, and usage without formal mechanisms in place.</p><p>By providing end-to-end visibility into how data originates, is transformed, and is consumed, data lineage creates transparency into the responsibilities associated with each stage of data processing. From an accountability perspective, lineage enables faster and more precise issue resolution.</p><blockquote>When data quality issues, failures, or inconsistencies arise, lineage allows teams to quickly identify the responsible upstream system, process, or transformation and engage the appropriate owner. This reduces ambiguity, prevents blame diffusion, and supports a culture of measurable responsibility.</blockquote><h4>Data Lineage Graphs</h4><p><strong>Data Lineage Graphs</strong> are visual representations of how data moves, transforms, and flows across an organization’s data ecosystem. They illustrate the relationships between data sources, datasets, pipelines, transformations, reports, dashboards, applications, and consumers. The upstream and downstream lineage graphs help answer the following questions:</p><ul><li><strong>Upstream lineage:</strong> Where does the data originate? Sources may include tables, files, or upstream processes. Upstream lineage is particularly useful for tracing source system failures and changes in transformation logic.</li><li><strong>Downstream lineage:</strong> Who is using the data? Downstream consumers may include processes, views, or dashboards. Downstream lineage is especially valuable for assessing the impact of transformation logic changes on dashboards, jobs, and notebooks.</li></ul><p>The data lineage graph is a valuable artifact for architectural reviews and audits. Following image show how a data lineage graph looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*_7aac69CvMWrb81oxVoDyA.png" /><figcaption>Image by author: Checking data lineage to explore upstream/downstream graphs</figcaption></figure><blockquote>In data lineage, upstream and downstream describe the direction of data flow and dependency across systems, pipelines, and reports.</blockquote><p>I hope this article offered a clear primer on the third key dimension of data governance. As promised, I’ll explore more dimensions in greater depth in the upcoming articles, so stay tuned. Topics like these are also covered in the Governance, Risk and Compliance (GRC) Specialist course offered through Datafence Cloud Academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbd85fdb08c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk about Data Governance — Dimension 3 — Data Classification Policies]]></title>
            <link>https://mkukreja1.medium.com/lets-talk-about-data-governance-dimension-3-data-classification-policies-ee53b3bcc311?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee53b3bcc311</guid>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 20:51:13 GMT</pubDate>
            <atom:updated>2026-10-29T20:52:27.917Z</atom:updated>
            <content:encoded><![CDATA[<h4>Protect what matters using the discipline of identifying, categorizing, and managing data according to its business value, sensitivity, and regulatory requirements.</h4><p>Towards the end of the last article we discussed an alternative approach to managing sensitive data that offers greater flexibility, It enables organizations control how much data is exposed, rather than choosing between fully hiding it and exposing it entirely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*pFovsz_Rudo25cVbVGRjRA.png" /><figcaption>Image by author — Dimension 3 — Data Classification Policies</figcaption></figure><blockquote><strong>Data classification policies</strong> impose a systematic process of organizing data into defined categories based on factors such as its sensitivity, business value, regulatory impact, and risk level.</blockquote><p>By classifying data, organizations can determine who should have access to it, how it must be protected, and which policies and controls apply. For example, highly sensitive data such as PII or financial records may require encryption, restricted access, and strict retention rules, while public or low‑risk data can be more openly shared with minimal controls. Common classification levels include categories such as <strong>Public</strong>, <strong>Confidential</strong>, and <strong>Restricted</strong>, though organizations often tailor these to their specific business and regulatory needs.</p><blockquote>Data classification forms the foundation for scalable data protection, access control, and governance.</blockquote><p>In modern data platforms, data classification can be implemented through both <strong>manual </strong>and <strong>automated </strong>mechanisms.</p><h3>Automated data classification</h3><p>Automated data classification is a capability that automatically discovers, classifies, and tags sensitive data — such as personally identifiable information (PII), financial data, and regulated attributes often using <strong>AI‑driven data scanning and detection techniques</strong>. The classification process analyzes metadata and data content to identify sensitive elements and applies standardized classification tags directly to supported data assets at scale.</p><p>These automatically generated classification tags become first‑class <strong>governance metadata</strong> within the catalog and can be leveraged to enforce downstream data protection and access control policies. By integrating automated classification with policy enforcement, modern data platforms enable organizations to operationalize data governance, reduce manual effort, and consistently protect sensitive data across large and evolving data estates, while maintaining scalability and regulatory compliance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*OW5zxLUJlCQDqPsy5hcZ9w.png" /><figcaption>Image by author —Example results of an automated data classification scan</figcaption></figure><h3>Automated data classification</h3><p>Manual data classification is a user‑driven approach for identifying, labeling, and managing data sensitivity using explicitly defined metadata, rather than automated AI scanning. In this model, data owners, stewards, or platform administrators intentionally apply classification tags to data assets based on business context, regulatory requirements, or domain knowledge. Manual classification is typically implemented using <strong>governed tags</strong> to securable objects such as catalogs, schemas, tables, views, or columns.</p><h4>Governed tags</h4><p>Governance tags are <strong>standardized labels</strong> that are applied to resources, data, or content to enable consistent classification, management, and control across an organization. They are commonly used to support policy-based access control, data cataloging and discoverability, cost and risk visibility, and scalable compliance without manual effort. Data classification also plays a critical role in:</p><ul><li><strong>Security:</strong> enforcing appropriate protection controls aligned to data sensitivity to minimize breach risk.</li><li><strong>Compliance:</strong> meeting regulatory and legal obligations such as privacy, data protection, and retention mandates.</li><li><strong>Data governance:</strong> establishing consistent standards for data handling, ownership, and accountability.</li><li><strong>Chargebacks and cost management:</strong> enabling domain‑ or classification‑based cost allocation and financial controls.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*iQYJe4NUAvdEnGU7bk9oQQ.png" /><figcaption>Image by author — Assigning custom governed tag to the credit_card column</figcaption></figure><p>The key question now is how governed tags help us manage data classification? Well its done using a combination of <strong>Attribute-Based Access Control (ABAC) </strong>and <strong>Fine‑Grained Access Control (FGAC).</strong></p><h4>Attribute‑based access control</h4><p>Using governed tags created previously, <strong>Attribute-Based Access Control (ABAC)</strong> evaluates data attributes at query time to determine access. These tags are assessed against defined access policies, allowing the system to dynamically filter, mask, or exclude sensitive information — such as PII — based on the user’s attributes, role, and context. This ensures that only authorized data is returned while enforcing consistent data protection without hard‑coded rules.</p><p>ABAC is a governance model that enforces policies such as row-level filtering to dynamically hide unauthorized rows and column-level masking to <strong>obfuscate </strong>sensitive fields. These controls are applied at query execution time, ensuring that access responds immediately as governed tags or policies change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*ypQ4bjKUnS-5IlMJdsc31g.png" /><figcaption>Image by author — ABAC enforcing row and column level controls</figcaption></figure><h4><strong>Fine‑Grained Access Control (FGAC)</strong></h4><p>While ABAC defines policies using governed tags, FGAC provides an enforcement engine that evaluates these policies at query time. The policy itself does not alter the data or permissions upfront; instead, FGAC applies it dynamically at query execution time. During query evaluation, the policy is assessed against the user’s attributes and the governed tags on the data, and the appropriate controls — such as masking or filtering — are enforced in real time.</p><p>FGAC policies can be applied at table, schema, or catalog level. Table‑level policies target a single asset, schema‑level policies cover all tables within that schema, and catalog‑level policies propagate across every schema and table for broad, consistent enforcement.</p><p>Here is how the policy enforcement flow looks like:</p><p>Fine‑Grained Access Control (FGAC) and Attribute‑Based Access Control (ABAC) are closely intertwined and work together to enforce modern data governance at scale. The following flow should hopefully clarify the inner workings of FGAC and APAC.</p><ol><li><strong>Governed tags are created and assigned</strong> to data assets (catalogs, schemas, tables, or columns) to describe attributes such as sensitivity, domain, or region.</li><li><strong>ABAC policies are defined</strong> at the catalog, schema, or table level, specifying how data with tags should be governed.</li><li><strong>A user submits a query</strong> against a data asset.</li><li><strong>Catalog identifies the user context</strong>, including user identity and group memberships.</li><li>Tags associated with the requested data are evaluated against the relevant ABAC policies.</li><li><strong>FGAC rules are enforced dynamically</strong>, applying row‑level filtering and/or column‑level masking as defined by the policies.</li><li><strong>The final query results are returned</strong>, reflecting only the data the user is permitted to see under the active policies.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*L2STp0nkFgZwQTokzvSgUg.png" /><figcaption>Image by author — PII redaction in real-time using ABAC andFGAC</figcaption></figure><p>I hope this article offered a clear primer on the third key dimension of data governance. As promised, I’ll explore more dimensions in greater depth in the upcoming articles, so stay tuned. Topics like these are also covered in the Governance, Risk and Compliance (GRC) Specialist course offered through Datafence Cloud Academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee53b3bcc311" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk about Data Governance — Dimension 2— Data Privacy & Regulatory Compliance]]></title>
            <link>https://mkukreja1.medium.com/lets-talk-about-data-governance-dimension-2-data-privacy-regulatory-compliance-85db56233c5a?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/85db56233c5a</guid>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 18:15:43 GMT</pubDate>
            <atom:updated>2026-10-29T20:52:21.244Z</atom:updated>
            <content:encoded><![CDATA[<h4>How organizations define, discover and protect personal data without losing its value.</h4><p>Data drives growth and innovation, but it has also been monetized in ways that stretch, or even violate, ethical boundaries: used without regard for privacy or informed consent and, at its extremes, to shape opinions and influence behavior. That is why responsible data governance and stronger regulatory oversight matter, so data can serve society without compromising trust or individual rights. This article takes a closer look at another critical dimension of data governance — <strong>Data Privacy &amp; Regulatory Compliance.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*ynBY_22wgNvF1LMWZe9sAg.png" /><figcaption>Image by author — Dimension 2 — Data Privacy &amp; Regulatory Compliance</figcaption></figure><p>Data privacy and regulatory compliance standards are designed to help<br>organizations meet global data protection, privacy, and security obligations. Modern data platforms align their controls with widely<br>recognized international frameworks and regulations, including <strong>GDPR </strong>and <strong>CCPA</strong>. These standards emphasize strong governance of customer data, ensuring that personal and sensitive information is processed lawfully and transparently, and for clearly defined purposes.</p><blockquote>Customers retain ownership and control of their data, while the data platform acts as a data processors under applicable privacy laws.</blockquote><h3>From awareness to accountability</h3><p>Earlier regulations, such as HIPAA, drew attention to the need to protect personal data, but enforcement was often limited and inconsistent. That changed in 2018, when the European Union enacted the GDPR. It redefined standards for the ethical collection, storage and use of personal data, and backed them with substantial fines and penalties. Individuals now have strong rights over their data: to be informed, to access and correct it, to request deletion in certain cases, to object to processing for marketing or profiling, and to opt out of its sale or sharing.</p><h3>What counts as PII?</h3><p><strong>Personally Identifiable Information (PII)</strong> is any information that can be used, on its own or combined with other data, to identify a specific individual. Direct identifiers include government-issued IDs such as passport or Social Security numbers; indirect identifiers include email addresses, phone numbers, IP addresses and location data that can be linked to a person. Organizations must ensure lawful collection, purpose limitation, secure storage, restricted access and proper disposal of PII throughout its lifecycle.</p><h4>PII Lifecycle: Define, Discover, Handle</h4><p>PII lifecycle is the process of identifying and locating PII across an organization’s data landscape. Its goal is to answer three critical questions:</p><ol><li>Where does the PII live?</li><li>What type of PII exists (direct or indirect)?</li><li>How it is being used?</li></ol><p>The PII lifecycle includes scanning structured data such as databases, data warehouses, data lakes, and lakehouses, as well as unstructured data like documents, logs, emails, and files stored in cloud platforms. Effective PII<br>handling creates visibility into sensitive data that may otherwise be hidden or inconsistently labeled. The following stages represent the recommended lifecycle for handling Personally Identifiable Information (PII).</p><ul><li><strong>Define</strong> : In this stage, the Data Protection Officer, Privacy Office, Legal and Compliance teams, and Information Security offices agree on what counts as <strong>direct </strong>and <strong>indirect </strong>identifiers. In a federated model, these central standards flow to business domains, where data owners and stewards <strong>identify</strong>, <strong>classify </strong>and <strong>label PII</strong> in their own datasets.</li><li><strong>Discover </strong>: Finding where PII lives, what type it is, and how it is being used. Automated techniques such as pattern matching, machine-learning classifiers and metadata analysis scan structured and unstructured data, and data owners and stewards validate the results. PII discovery typically combines automated techniques — such as pattern matching, keyword searches, machine-learning classifiers, and metadata analysis — with human validation by data owners and stewards. Following is a list of some well-known tools and services that can automate the PII discovery process:<br><strong>Microsoft Purview</strong>: Built-in PII discovery and classification across Azure environments.<br><strong>AWS Macie</strong>: PII and sensitive data discovery for Amazon S3<br><strong>Google Cloud DLP</strong>: Pattern- and ML-based PII detection across GCP services<br><strong>Databricks Unity Catalog</strong>: Column-level lineage, tagging, and integration with PII detection tools<br><strong>BigID</strong>: ML-driven discovery of PII, sensitive data, and data relationships across on-prem and cloud<br><strong>Collibra Protect</strong>: Integrates governance metadata with sensitive data discovery<br><strong>Informatica Data Privacy Management</strong>: Enterprise-grade PII discovery,<br>classification, and risk scoring</li><li><strong>Handle </strong>: Once PII is discovered, several techniques including<strong> masking, anonymization, pseudonymization </strong>&amp; <strong>tokenization </strong>are used to reduce privacy risk while still enabling analysis, testing and sharing. The table below summarizes some well-known techniques for handling PII.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*TMw4X2uI9URyZ5iH7kEFTQ.png" /><figcaption>Image by author — PII handling techniques</figcaption></figure><p>For a detailed explanation of how each PII handling method is implemented, I recommend reading my previous article below:</p><p><a href="https://medium.com/aws-in-plain-english/regulatory-compliance-gdpr-and-ccpa-using-delta-lake-fa0582b2fc2d">https://medium.com/aws-in-plain-english/regulatory-compliance-gdpr-and-ccpa-using-delta-lake-fa0582b2fc2d</a></p><p>It is important to note that while the methods discussed above effectively obscure PII through <strong>self-coded data transformation techniques</strong>, they can sometimes be complex and challenging to implement. Fortunately, there is a simpler yet highly effective alternative:</p><h4>Obscuring PII using masking functions</h4><p>In addition to the techniques discussed above, PII obscuring using functions is a widely adopted approach that relies on custom or built-in transformation functions to reduce the exposure of sensitive data while maintaining usability for analytics, testing, or operational purposes. These functions can be applied at ingestion time, during data transformation<br>pipelines, or at query time, enabling organizations to protect PII without physically removing it from the underlying dataset.<br>Most modern data platform provide data masking functions that replace all or part of a sensitive value with fixed or dynamic patterns — for example, displaying only the last four digits of a Social Security Number or credit card number. Function-based PII obscuring is particularly effective when combined with data classification, role-based access controls, and policy enforcement, ensuring that only authorized users can view clear-text values while others see masked, hashed, or tokenized data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*skCvQQBPmGngV_NuSYdkHg.png" /><figcaption>Image by author — Data masking functions</figcaption></figure><p>This approach helps organizations meet privacy and compliance requirements, reduce risk, and preserve analytical value, making it a core component of modern data governance and <strong>privacy-by-design</strong> strategies.</p><p>Each PII handling technique offers a different balance between data utility and privacy protection, and their suitability depends on factors such as regulatory requirements, intended use, and risk tolerance. Because anonymization irreversibly removes the ability to identify individuals, while pseudonymization retains a controlled link to original identities, each method has distinct advantages and limitations.</p><p>Rather than prescribing a single approach, this article presents all techniques so readers can evaluate and select the one that best aligns with their PII-handling objectives, compliance obligations, and operational needs.</p><blockquote>In addition to PII techniques discussed above, there is another approach to managing sensitive data that offers greater flexibility — enabling organizations to control how much data is exposed, rather than choosing between fully hiding it and exposing it entirely — Data Classification Policies. We will talk about it in greater detail in the upcoming article.</blockquote><p>I hope this article offered a clear primer on the second key dimension of data governance. As promised, I’ll explore more dimensions in greater depth in the upcoming articles, so stay tuned. Topics like these are also covered in the Governance, Risk and Compliance (GRC) Specialist course offered through Datafence Cloud Academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85db56233c5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk about Data Governance — Dimension 1 — Data Access Policies]]></title>
            <link>https://mkukreja1.medium.com/lets-talk-about-data-governance-dimension-1-data-access-policies-056dcc69e155?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/056dcc69e155</guid>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 18:19:26 GMT</pubDate>
            <atom:updated>2026-10-19T18:19:26.041Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ensuring the right people have access to the right data at the right time with the right controls.</h4><p>In the last article, we introduced the key dimensions of data governance and discussed their importance in building a robust governance framework. I also promised that we would explore each dimension in greater depth in future articles. This article delivers on that promise and takes a closer look at one of those critical dimensions — <strong>Data Access Policies.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYsDus8nPwsUFOM88pS4mQ.png" /><figcaption>Image by author — Dimension — Data Access Policy</figcaption></figure><p>At a high level, <strong>data access policies</strong> define <strong>who </strong>can access <strong>which </strong>data, at <strong>what </strong>level of detail, and under what <strong>conditions</strong>. These policies ensure that data is used securely and responsibly, in compliance with organizational standards and regulatory requirements.</p><h3>The four questions every data access policy needs to answer</h3><ul><li><strong>Who</strong>: Defines the authorized <strong>users</strong>, <strong>groups</strong>, <strong>roles</strong>, or <strong>service accounts </strong>that are permitted to access data. This is typically aligned with business domains or functions and supports access models such as role-based access control (RBAC) and attribute-based access control (ABAC).</li><li><strong>What data</strong>: Specifies the data assets that can be <strong>accessed</strong>, including catalogs, schemas, tables, views, files, or models. Access is granted only to datasets that are relevant to a user’s role or business responsibility.</li><li><strong>Level of detail</strong>: Determines the <strong>granularity </strong>of access, such as read-only versus read-write permissions, row-level filtering, and column-level visibility or masking for sensitive information such as PII.</li><li><strong>Under which conditions</strong>: Establishes contextual <strong>access constraints</strong>, such as the environment (development, test, or production), and compliance, audit, legal, or policy-driven requirements.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*dw1wtYnDSG62IOirzR8Sew.png" /><figcaption>Image by author — Data Access Policy</figcaption></figure><h3>To whom are data access policies granted ?</h3><p>Modern data platforms manage access through identities, including <strong>users</strong>, <strong>groups</strong>, and <strong>service principals</strong>. To maintain a scalable and governable access model, these identities should be structured around business domains and organizational responsibilities. Furthermore, access permissions should be granted at the group level rather than directly to individual users. This simplifies administration, promotes consistency, and makes it easier to enforce least-privilege access principles across the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*GzBypBq9Khbv_6EnGsKbaQ.png" /><figcaption><em>Image by author — Granting data access policies to users, groups, and service principals</em></figcaption></figure><h3>How are data access policies implemented?</h3><p>The primary objective of data access policies is to enforce the <strong>principle of least privilege</strong>, ensuring that users are granted only the minimum level of access required to perform their responsibilities. This approach significantly reduces the risk of unauthorized access and data exposure.</p><blockquote>The principle of least privilege states that users, roles, and systems should be granted only the minimum access necessary to perform their authorized tasks. This reduces security risk by limiting unnecessary exposure to data, systems, and sensitive operations.</blockquote><h4>Data Access Control Models</h4><p>Data access control models provide the framework for implementing data access policies — assigning, managing, and governing permissions to ensure that users can access only the data and resources they are authorized to use. Following are some well-known data acccess cotrol models:</p><h4><strong>Access control lists (ACL)</strong></h4><p>ACL is a resource-level security model that specifies which users, groups, or service principals are authorized to access a particular resource (tables, views etc.) and what operations they can perform. Because permissions are assigned directly to each resource, ACLs provide a simple and intuitive access control model. However, as the number of resources and identities increases, managing ACLs can become complex, time-consuming, and prone to inconsistencies.</p><h4><strong>Role-based access control (RBAC)</strong></h4><p>In the <strong>RBAC</strong> model, permissions are assigned to <strong>roles </strong>that represent specific job functions, and users gain access through their assigned roles. This approach improves scalability, simplifies administration, and supports auditing and governance. However, organizations must carefully manage role design to avoid <strong>role explosion</strong>, where an excessive number of roles becomes difficult to maintain.</p><h4><strong>Fine‑grained access control (FGAC)</strong></h4><p><strong>Fine‑grained access control (FGAC)</strong> is a security authorization model that governs access to data assets across <strong>multiple hierarchical scopes</strong>, including the catalog, schema, and individual securable objects such as tables, views, functions, and columns. FGAC enables precise, object‑level permission management by explicitly defining and enforcing privileges based on the operation type (e.g., SELECT, INSERT, UPDATE, DELETE, EXECUTE, ADMIN).</p><p>Under FGAC, access can be <strong>progressively constrained</strong>. For example, a principal (user, group, or service identity) may be granted read‑only access at the catalog level, restricted access to specific schemas within that catalog, and further limited to a subset of tables or columns within a schema. This hierarchical and explicit grant model ensures tight control over data exposure and usage.</p><h4><strong>Attribute-based access control (ABAC)</strong></h4><p>ABAC is a governance model that enforces policies such as row-level filtering to dynamically hide unauthorized rows and column-level masking to obfuscate sensitive fields. These controls are applied at <strong>query execution</strong> time using <strong>governed tags. </strong>These tags are assessed against defined access policies, allowing the system to dynamically filter, mask, or exclude sensitive information — such as PII — based on the user’s attributes, role, and context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*ypQ4bjKUnS-5IlMJdsc31g.png" /><figcaption>Image by author — ABAC enforcing row and column level controls</figcaption></figure><blockquote>It is important to understand that while ABAC defines policies using governed tags, FGAC provides an enforcement engine that evaluates these policies at query time.</blockquote><p>To sum up, data access policies should be centered on a group‑based, least‑privilege security model, with groups preferably aligned to business domains and clearly defined access levels to ensure scalable, auditable, and well‑governed access.</p><p>I hope this article offered a clear primer on the first the key dimension of data governance. As promised, I’ll explore each dimension in greater depth in the upcoming articles, so stay tuned. Topics like these are also covered in the Governance, Risk and Compliance (GRC) Specialist course offered through Datafence Cloud Academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=056dcc69e155" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk about Data Governance]]></title>
            <link>https://mkukreja1.medium.com/lets-talk-about-data-governance-30d912a6f3db?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/30d912a6f3db</guid>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 18:55:23 GMT</pubDate>
            <atom:updated>2026-10-15T18:55:23.076Z</atom:updated>
            <content:encoded><![CDATA[<h4>Evolving data assets into governed, trustworthy data products that create consistent and measurable value.</h4><p>Lately, I’ve noticed a clear shift across the industry — organizations are moving away from simple data assets that merely deliver value, toward fully governed data products that deliver value with confidence. This transition isn’t just about packaging data differently; it’s about elevating trust, reliability, accountability, and usability so data becomes a dependable product rather than a loose collection of tables.</p><p>But the path to strong data governance is long and demanding — governed data products requires discipline, maturity, and a clear framework. A well-designed governance strategy not only safeguards organizational data assets but also enables organizations to fully realize the value of analytics by fostering trust among business users and providing assurance to security, risk, and compliance stakeholders.</p><blockquote>It’s not just a technical journey; it’s an organizational transformation that touches people, processes, and culture.</blockquote><h3>Implementing a robust data governance strategy</h3><p>At its core, data governance brings together a set of complementary practices that collectively establish <strong>trust</strong>, protect sensitive information, and ensure <strong>consistent</strong>, <strong>responsible </strong>use of data across the organization. When implemented effectively, these practices form a cohesive framework that balances control with enablement, allowing data products to be shared <strong>confidently </strong>and <strong>consumed </strong>at scale.</p><blockquote>So how does one begin tackling the challenge?</blockquote><p>Data governance strategy typically encompasses several key areas, each contributing to the organization’s ability to safeguard data while maximizing its analytical value. Together, the governance dimensions as defined in the image below define how data is owned, secured, classified, certified, monitored, and evolved over time — ensuring that users can trust not only the data itself, but also the processes and controls that support it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*9P7QVlDPengJx4zHgkqjZg.png" /><figcaption>Image by author — Data governance standards and policies</figcaption></figure><p>Today, let’s take a high‑level look at how each governance dimension plays a role in keeping data secure, trustworthy, and compliant with regulatory requirements. And don’t worry — we’ll dive deep into every one of these dimensions in the articles that follow.</p><h4>Data access policies</h4><p>At a high level, access policies define <strong>who </strong>can access which data, at <strong>what</strong> level of detail, and under <em>what conditions</em>. These policies ensure that data is used securely and responsibly, in compliance with organizational standards and regulatory requirements.</p><h4>Data privacy and regulatory compliance standards</h4><p>Data privacy and regulatory compliance standards ensure that organizations meet global data protection requirements — such as GDPR and CCPA — while upholding strict obligations around privacy, security, and responsible data handling.</p><h4>Data classification policies</h4><p>Data classification policies impose a systematic process of organizing data into defined categories based on factors such as its sensitivity, business value, regulatory impact, and risk level. By classifying data, organizations can determine <strong>who </strong>should have access to it, <strong>how </strong>it must be protected, and <strong>which </strong>policies and controls apply.</p><h4>Data lineage tracking policies</h4><p>Data lineage is the practice of tracking <strong>how </strong>data is used as it flows through systems — from where it’s <strong>created </strong>to where it’s <strong>consumed</strong>. It involves systematic documentation of data origins, flow, dependencies, transformations, and downstream consumption across systems throughout the data lifecycle.</p><h4>Data lifecycle management policies</h4><p>Data lifecycle management policy is a formal framework that establishes <strong>how long</strong> an organization retains information, the <strong>purpose </strong>for retaining it, <strong>where </strong>it is stored, and the conditions and <strong>methods </strong>for its secure disposal.</p><h4>Data quality standards</h4><p>Among the four Vs of big data, data veracity emphasizes the key dimensions of accuracy, trustworthiness, and reliability. Data quality standards measure how well data aligns with key business objectives based on these dimensions.</p><h4>Data observability standards</h4><p>Data observability standards define how organizations monitor and ensure the health, reliability, and trustworthiness of data as it moves through modern data pipelines and ultimately powers data products.</p><h4>Data stewardship</h4><p>Data stewardship is the human accountability layer of data governance — the set of roles and responsibilities that ensure data is accurate, trusted, well-understood, and used appropriately across an organization.</p><blockquote>In short, data governance policies define the rules of engagement, and data stewards turn those rules into reality.</blockquote><p>I hope this article offered a clear primer on the key dimensions of data governance. As promised, I’ll explore each dimension in greater depth in the upcoming articles, so stay tuned. Topics like these are also covered in the Governance, Risk and Compliance (GRC) Specialist course offered through Datafence Cloud Academy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgUGmHvko1K02WE20m6JNg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30d912a6f3db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Trusted Data Platforms with Azure Databricks and GenAI]]></title>
            <link>https://mkukreja1.medium.com/building-trusted-data-platforms-with-azure-databricks-and-genai-156ec6ab7003?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/156ec6ab7003</guid>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 22:23:18 GMT</pubDate>
            <atom:updated>2026-09-29T22:23:18.754Z</atom:updated>
            <content:encoded><![CDATA[<h4>A comprehensive guide covering Lakehouse architecture, Delta Lake, Unity Catalog governance, data quality frameworks, secure data product design, and practical GenAI integration for enterprise analytics.</h4><p>In an era where data has become the backbone of every modern enterprise, organizations are under immense pressure to build platforms that are not only scalable and high‑performing but also governed, secure, and trustworthy. The rapid evolution of cloud technologies, the rise of Lakehouse architectures, and the explosive growth of GenAI have created both unprecedented opportunities and significant risks. This is the landscape in which <em>Building Trusted Data Platforms with Azure Databricks and GenAI</em> has become an essential guide for data leaders, architects, and engineering teams worldwide.</p><h4>A Book Built for the Modern Data Reality</h4><p>Most enterprises today struggle with fragmented data systems, inconsistent governance, unreliable pipelines, and unclear ownership models. As organizations adopt Databricks, Delta Lake, Unity Catalog, and AI/ML workloads, they often lack a unified blueprint for building platforms that are both innovative and compliant.</p><blockquote>My book fills that gap.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*W50Ys3mCq-TIxcHz6JCQMQ.png" /><figcaption>Image by author</figcaption></figure><p>It provides a <strong>practical, hands‑on framework</strong> for designing Lakehouse architectures that balance agility with governance, performance with cost efficiency, and innovation with regulatory responsibility. It is one of the few resources that connects <strong>data engineering, governance, security, and GenAI</strong> into a single, coherent operating model.</p><h4>Governance Is No Longer Optional</h4><p>With increasing regulatory pressure — GDPR, CCPA, PCI, HIPAA, ISO, SOC — organizations must treat governance as a first‑class engineering requirement. Your book shows how Unity Catalog, Purview, lineage, quality frameworks, and domain‑driven ownership can be embedded directly into Databricks Lakehouse design.</p><h4>Growing Demand For Trusted Data</h4><p>AI and GenAI systems are only as reliable as the <strong>data products</strong> that feed them. As enterprises accelerate adoption of LLMs, agentic workflows, and AI‑driven analytics, the need for <strong>high‑quality, well‑governed, domain‑owned data products</strong> becomes critical. GenAI models depend on consistent schemas, accurate metadata, strong lineage, and trustworthy semantics to produce reliable outputs. Poorly governed data products lead to hallucinations, biased predictions, compliance violations, and operational risk. My book emphasizes the foundational role of <strong>trusted data products</strong> — built with Delta Lake, Unity Catalog, quality checks, lineage, and domain stewardship — as the backbone of safe, scalable, and responsible AI. By ensuring that every data product is discoverable, certified high‑quality, and compliant, organizations can confidently power GenAI workloads that are accurate, explainable, and enterprise‑ready.</p><h4>What does a Futuristic Data Platform Look Like?</h4><p>Growing demands of today’s data analytics requires a next-generation, future-ready data platform that transcends traditional analytics to become the intelligent backbone of the organization should embody the following characteristics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vaG5qHbIEwsTmTphOWj2Bg.png" /><figcaption>Image by author — Hallmarks of future ready data platform</figcaption></figure><blockquote>Why are the blocks structured in the shape of a pyramid ?</blockquote><p>Each block in the data platform strengthens the next until data transforms into actions. Together, these layers create a cohesive technology stack in which each layer serves as the foundation for the one above it. Missing a single layer weakens the structure, and the pyramid loses its balance. To understand how the pyramid achieves and maintains its balance.</p><p>The evolution of future data platforms is a re-imagining of data-driven decision-making. It’s a re-conceptualization of the journey of data — production, transformation, distribution, and consumption. Modern data platforms are quickly becoming corporate growth enablers, increasingly<br>defining the core difference between organizational success and failure.<br>A well-designed future data platform represents a convergence of data-driven intelligence, modern data architecture, cutting-edge cloud-enabled services and frameworks, automation, and operational excellence.</p><blockquote>The real question is: what are the defining hallmarks of a truly futuristic and cutting-edge data platform?</blockquote><ul><li>Uses an easy-to-use, scalable base infrastructure (preferably using the cloud) to sustain critical loads with optimal performance.</li><li>A data architecture that supports both batch and streaming workloads, adapts to varying data formats, and supports the ever-increasing demands of consumers.</li><li>Deliver a certain level of trust to its users by delivering federated governance, high data quality, and certified data products.</li><li>Facilitate a secure and seamless mechanism for distributing data across diverse internal domains and external entities.</li><li>Creates a centralized repository that addresses core MDM challenges for key data entities, including duplication, inconsistency, and accuracy issues.</li><li>Leverage automation to streamline infrastructure and code deployments.</li><li>Ensure health, visibility, and reliability of data using trustworthy data observability practices.</li><li>Follow ethical AI standards by adhering to industry best practices.</li></ul><p>Together, these elements form the blueprint for future-ready data platforms — systems that are not only well-governed, resilient, and intelligent, but also adaptable to continuous change. They enable organizations to operate with confidence in an environment defined by rapid data growth, evolving regulatory expectations, and accelerating advances in AI.</p><p>Overall, a next-generation, future-ready data platform transcends<br>traditional analytics to become the intelligent backbone of any organization.</p><p>I wasn’t able to cover every topic above in depth, but if you found this material valuable, you’ll benefit even more from my book, where each concept is explored thoroughly with hands‑on guidance and real‑world architectural patterns.</p><p>I hope this article has given you clarity and direction on the emerging trends shaping the future of data platforms. These concepts — along with a deeper exploration of modern Lakehouse patterns, Databricks best practices, and GenAI‑driven architectures — are covered extensively in my <strong>Databricks Certified Data Engineer and GenAI Engineer</strong> course offered through <strong>Datafence Cloud Academy</strong>, which I teach live online on weekends for practitioners looking to advance their expertise.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=156ec6ab7003" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Mesh — A new Level of Data Collaboration using Self-Serve Analytics]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/data-mesh-a-new-level-of-data-collaboration-using-self-serve-analytics-77e316127c6d?source=rss-4076fc16cb6a------2"><img src="https://cdn-images-1.medium.com/max/844/1*CsPpfYIsXw9YTn3W3vbBrw.png" width="844"></a></p><p class="medium-feed-snippet">In this article, we will learn how Amazon DataZone promotes the idea of &#x201C;self-serve data analytics&#x201D;. by simplifying the data collaboration&#x2026;</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/data-mesh-a-new-level-of-data-collaboration-using-self-serve-analytics-77e316127c6d?source=rss-4076fc16cb6a------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/data-mesh-a-new-level-of-data-collaboration-using-self-serve-analytics-77e316127c6d?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/77e316127c6d</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data-fabric]]></category>
            <category><![CDATA[data-lake]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Wed, 28 Feb 2024 02:24:34 GMT</pubDate>
            <atom:updated>2024-02-29T04:10:29.005Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Master Data Management — Building the Golden Record]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/master-data-management-building-the-golden-record-b31eaf0abfdc?source=rss-4076fc16cb6a------2"><img src="https://cdn-images-1.medium.com/max/600/1*EfgCCvpeXGVPAeZza-R9mg.png" width="600"></a></p><p class="medium-feed-snippet">In this article, we will learn how to build the &#x201C;Golden Record&#x201D; in MDM using an unsupervised linking model Splink embedded within&#x2026;</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/master-data-management-building-the-golden-record-b31eaf0abfdc?source=rss-4076fc16cb6a------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/master-data-management-building-the-golden-record-b31eaf0abfdc?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b31eaf0abfdc</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[golden-record]]></category>
            <category><![CDATA[mdm]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Sun, 11 Feb 2024 20:25:31 GMT</pubDate>
            <atom:updated>2024-02-14T03:03:58.791Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[2023 — Year of Cloud Resource Cost Optimization]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/2023-year-of-cloud-resource-cost-optimization-186c3eb6657?source=rss-4076fc16cb6a------2"><img src="https://cdn-images-1.medium.com/max/640/1*pRA0NGc_wyBN94nghgVlBA.jpeg" width="640"></a></p><p class="medium-feed-snippet">In this article, we will focus on some key methods to effectively optimize your AWS cloud resource costs.</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/2023-year-of-cloud-resource-cost-optimization-186c3eb6657?source=rss-4076fc16cb6a------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/2023-year-of-cloud-resource-cost-optimization-186c3eb6657?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/186c3eb6657</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 20:40:59 GMT</pubDate>
            <atom:updated>2023-06-26T01:04:10.318Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Use Delta Lake as the Master Data Management (MDM) Source for Downstream Applications]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/data-science/use-delta-lake-as-the-master-data-management-mdm-source-for-downstream-applications-882250dc0b4a?source=rss-4076fc16cb6a------2"><img src="https://cdn-images-1.medium.com/max/600/1*t-Y5K4XntRUXuEDCsn5GQA.png" width="600"></a></p><p class="medium-feed-snippet">In this article, we will try to understand how the output from Delta Lake change feed can be used to feed downstream applications</p><p class="medium-feed-link"><a href="https://medium.com/data-science/use-delta-lake-as-the-master-data-management-mdm-source-for-downstream-applications-882250dc0b4a?source=rss-4076fc16cb6a------2">Continue reading on TDS Archive »</a></p></div>]]></description>
            <link>https://medium.com/data-science/use-delta-lake-as-the-master-data-management-mdm-source-for-downstream-applications-882250dc0b4a?source=rss-4076fc16cb6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/882250dc0b4a</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[delta-lake]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[change-data-capture]]></category>
            <category><![CDATA[databricks]]></category>
            <dc:creator><![CDATA[Manoj Kukreja]]></dc:creator>
            <pubDate>Sun, 05 Feb 2023 21:04:24 GMT</pubDate>
            <atom:updated>2023-02-08T04:25:55.699Z</atom:updated>
        </item>
    </channel>
</rss>