{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
        "slug": "dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/"
        },
        "title": "Check iSCSI client digest support before enforcing Elastic SAN CRC protection",
        "summary": "Volume-group checksum enforcement can reject clients that cannot supply the required header or data digests.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-10T00:27:01+00:00",
        "modified_at": "2026-09-10T01:23:49+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 234,
        "potentially_affected": "Azure Elastic SAN volume groups and iSCSI clients using their volumes.",
        "dse_recommendation": "Verify every client's digest capabilities and configuration before enforcing CRC protection at volume-group scope.",
        "primary_source": {
            "name": "Azure Elastic SAN networking concepts | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-networking",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>Elastic SAN supports CRC-32C verification for iSCSI headers and data. A volume-group property can enforce it, and every volume in that group inherits the setting. With enforcement enabled, connections lacking the required digest configuration are rejected.</p>\n<p>Microsoft warns that some operating systems lack header or data digest support, specifically identifying Fedora and downstream distributions as lacking data digests. It advises against enabling group enforcement for clients that cannot support those digests because their connections fail. <a href=\"https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-networking\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Inventory all clients of the volume group, including less frequently used recovery or maintenance hosts. Verify support against the actual operating system and initiator configuration.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends a client-by-client compatibility record before a group-wide change. Resolve unsupported clients through an approved storage design rather than assuming they negotiate the new requirement automatically. Keep the previous setting and a controlled recovery plan available. Treat this as an integrity and connection-compatibility decision, not a replacement for reviewing the separate network-access configuration.</p>\n<h2>Verification</h2>\n<p>In a controlled test, confirm the intended digest settings and reconnect representative supported clients. Check application reads and writes as well as session establishment. Record any rejected or unsupported client explicitly before extending enforcement to the shared group. A successful connection from one operating system is not sufficient evidence for the other clients that inherit the same volume-group policy.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-networking\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Azure Elastic SAN networking concepts</a>. Source retrieved September 9, 2026.</p>",
        "content_text": "Source facts\nElastic SAN supports CRC-32C verification for iSCSI headers and data. A volume-group property can enforce it, and every volume in that group inherits the setting. With enforcement enabled, connections lacking the required digest configuration are rejected.\nMicrosoft warns that some operating systems lack header or data digest support, specifically identifying Fedora and downstream distributions as lacking data digests. It advises against enabling group enforcement for clients that cannot support those digests because their connections fail. Microsoft Learn.\nApplicability\nInventory all clients of the volume group, including less frequently used recovery or maintenance hosts. Verify support against the actual operating system and initiator configuration.\nDSE recommendation\nDSE recommends a client-by-client compatibility record before a group-wide change. Resolve unsupported clients through an approved storage design rather than assuming they negotiate the new requirement automatically. Keep the previous setting and a controlled recovery plan available. Treat this as an integrity and connection-compatibility decision, not a replacement for reviewing the separate network-access configuration.\nVerification\nIn a controlled test, confirm the intended digest settings and reconnect representative supported clients. Check application reads and writes as well as session establishment. Record any rejected or unsupported client explicitly before extending enforcement to the shared group. A successful connection from one operating system is not sufficient evidence for the other clients that inherit the same volume-group policy.\nOfficial references\nMicrosoft Learn: Azure Elastic SAN networking concepts. Source retrieved September 9, 2026.",
        "content_markdown": "## Source facts\n\nElastic SAN supports CRC-32C verification for iSCSI headers and data. A volume-group property can enforce it, and every volume in that group inherits the setting. With enforcement enabled, connections lacking the required digest configuration are rejected.\n\nMicrosoft warns that some operating systems lack header or data digest support, specifically identifying Fedora and downstream distributions as lacking data digests. It advises against enabling group enforcement for clients that cannot support those digests because their connections fail. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-networking).\n\n## Applicability\n\nInventory all clients of the volume group, including less frequently used recovery or maintenance hosts. Verify support against the actual operating system and initiator configuration.\n\n## DSE recommendation\n\nDSE recommends a client-by-client compatibility record before a group-wide change. Resolve unsupported clients through an approved storage design rather than assuming they negotiate the new requirement automatically. Keep the previous setting and a controlled recovery plan available. Treat this as an integrity and connection-compatibility decision, not a replacement for reviewing the separate network-access configuration.\n\n## Verification\n\nIn a controlled test, confirm the intended digest settings and reconnect representative supported clients. Check application reads and writes as well as session establishment. Record any rejected or unsupported client explicitly before extending enforcement to the shared group. A successful connection from one operating system is not sufficient evidence for the other clients that inherit the same volume-group policy.\n\n## Official references\n\n[Microsoft Learn: Azure Elastic SAN networking concepts](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-networking). Source retrieved September 9, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Check iSCSI client digest support before enforcing Elastic SAN CRC protection",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/",
                "headline": "Check iSCSI client digest support before enforcing Elastic SAN CRC protection",
                "description": "Volume-group checksum enforcement can reject clients that cannot supply the required header or data digests.",
                "abstract": "Volume-group checksum enforcement can reject clients that cannot supply the required header or data digests.",
                "articleBody": "Source facts\nElastic SAN supports CRC-32C verification for iSCSI headers and data. A volume-group property can enforce it, and every volume in that group inherits the setting. With enforcement enabled, connections lacking the required digest configuration are rejected.\nMicrosoft warns that some operating systems lack header or data digest support, specifically identifying Fedora and downstream distributions as lacking data digests. It advises against enabling group enforcement for clients that cannot support those digests because their connections fail. Microsoft Learn.\nApplicability\nInventory all clients of the volume group, including less frequently used recovery or maintenance hosts. Verify support against the actual operating system and initiator configuration.\nDSE recommendation\nDSE recommends a client-by-client compatibility record before a group-wide change. Resolve unsupported clients through an approved storage design rather than assuming they negotiate the new requirement automatically. Keep the previous setting and a controlled recovery plan available. Treat this as an integrity and connection-compatibility decision, not a replacement for reviewing the separate network-access configuration.\nVerification\nIn a controlled test, confirm the intended digest settings and reconnect representative supported clients. Check application reads and writes as well as session establishment. Record any rejected or unsupported client explicitly before extending enforcement to the shared group. A successful connection from one operating system is not sufficient evidence for the other clients that inherit the same volume-group policy.\nOfficial references\nMicrosoft Learn: Azure Elastic SAN networking concepts. Source retrieved September 9, 2026.",
                "datePublished": "2026-09-10T00:27:01+00:00",
                "dateModified": "2026-09-10T01:23:49+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-295-check-iscsi-client-digest-support-before-enforcing-elastic-san-crc-protection/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Check iSCSI client digest support before enforcing Elastic SAN CRC protection"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 234,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Azure Elastic SAN networking concepts | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-networking"
                }
            }
        ]
    }
}