{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "slug": "dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor", "url": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/" }, "title": "Preserve long NPS expressions outside the console editor", "summary": "How can an NPS expression longer than 256 characters be maintained without invalidating it?", "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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "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-08T18:16:21+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 201, "potentially_affected": "Use this review when an approved NPS expression approaches or exceeds the graphical editor limit.", "dse_recommendation": "Keep the approved expression in a controlled change record and choose the documented command-based route when required.", "primary_source": { "name": "Use Regular Expressions in NPS", "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-crp-reg-expressions", "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": "

Source facts

\n

NPS supports regular expressions for network-policy attribute conditions and RADIUS realms. NPS console and MMC string fields have a 256-character entry limit, including regular-expression settings. Microsoft directs administrators to NETSH NPS commands for longer values. Editing an already configured longer value through those graphical tools invalidates it. Microsoft documentation.

\n

Applicability

\n

Use this review when an approved NPS expression approaches or exceeds the graphical editor limit. Identify the exact policy field, current expression, character count, and intended maintenance interface before changing the value.

\n

DSE recommendation

\n

Keep the approved expression in a controlled change record and choose the documented command-based route when required. Have another administrator compare the complete proposed value with that record. Review escaping, anchors, and the expected matches against the source syntax reference. Document that later graphical editing is excluded for this long-value configuration.

\n

Verification

\n

Inspect the configured value after the approved change and compare it character for character with the reviewed expression. Run representative matching and nonmatching inputs without altering the intended authentication design. Preserve the command, sanitized observations, and full expression for the next operator. Resolve truncation or unexpected modification before accepting the change.

\n

Official references

\n

Microsoft Learn: Use Regular Expressions in NPS. Source reviewed September 8, 2026.

", "content_text": "Source facts\nNPS supports regular expressions for network-policy attribute conditions and RADIUS realms. NPS console and MMC string fields have a 256-character entry limit, including regular-expression settings. Microsoft directs administrators to NETSH NPS commands for longer values. Editing an already configured longer value through those graphical tools invalidates it. Microsoft documentation.\nApplicability\nUse this review when an approved NPS expression approaches or exceeds the graphical editor limit. Identify the exact policy field, current expression, character count, and intended maintenance interface before changing the value.\nDSE recommendation\nKeep the approved expression in a controlled change record and choose the documented command-based route when required. Have another administrator compare the complete proposed value with that record. Review escaping, anchors, and the expected matches against the source syntax reference. Document that later graphical editing is excluded for this long-value configuration.\nVerification\nInspect the configured value after the approved change and compare it character for character with the reviewed expression. Run representative matching and nonmatching inputs without altering the intended authentication design. Preserve the command, sanitized observations, and full expression for the next operator. Resolve truncation or unexpected modification before accepting the change.\nOfficial references\nMicrosoft Learn: Use Regular Expressions in NPS. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nNPS supports regular expressions for network-policy attribute conditions and RADIUS realms. NPS console and MMC string fields have a 256-character entry limit, including regular-expression settings. Microsoft directs administrators to NETSH NPS commands for longer values. Editing an already configured longer value through those graphical tools invalidates it. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-crp-reg-expressions).\n\n## Applicability\n\nUse this review when an approved NPS expression approaches or exceeds the graphical editor limit. Identify the exact policy field, current expression, character count, and intended maintenance interface before changing the value.\n\n## DSE recommendation\n\nKeep the approved expression in a controlled change record and choose the documented command-based route when required. Have another administrator compare the complete proposed value with that record. Review escaping, anchors, and the expected matches against the source syntax reference. Document that later graphical editing is excluded for this long-value configuration.\n\n## Verification\n\nInspect the configured value after the approved change and compare it character for character with the reviewed expression. Run representative matching and nonmatching inputs without altering the intended authentication design. Preserve the command, sanitized observations, and full expression for the next operator. Resolve truncation or unexpected modification before accepting the change.\n\n## Official references\n\n[Microsoft Learn: Use Regular Expressions in NPS](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-crp-reg-expressions). Source reviewed September 8, 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-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "url": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Preserve long NPS expressions outside the console editor", "item": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "url": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/", "headline": "Preserve long NPS expressions outside the console editor", "description": "How can an NPS expression longer than 256 characters be maintained without invalidating it?", "abstract": "How can an NPS expression longer than 256 characters be maintained without invalidating it?", "articleBody": "Source facts\nNPS supports regular expressions for network-policy attribute conditions and RADIUS realms. NPS console and MMC string fields have a 256-character entry limit, including regular-expression settings. Microsoft directs administrators to NETSH NPS commands for longer values. Editing an already configured longer value through those graphical tools invalidates it. Microsoft documentation.\nApplicability\nUse this review when an approved NPS expression approaches or exceeds the graphical editor limit. Identify the exact policy field, current expression, character count, and intended maintenance interface before changing the value.\nDSE recommendation\nKeep the approved expression in a controlled change record and choose the documented command-based route when required. Have another administrator compare the complete proposed value with that record. Review escaping, anchors, and the expected matches against the source syntax reference. Document that later graphical editing is excluded for this long-value configuration.\nVerification\nInspect the configured value after the approved change and compare it character for character with the reviewed expression. Run representative matching and nonmatching inputs without altering the intended authentication design. Preserve the command, sanitized observations, and full expression for the next operator. Resolve truncation or unexpected modification before accepting the change.\nOfficial references\nMicrosoft Learn: Use Regular Expressions in NPS. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:21+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/" }, "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-20260908-050-preserve-long-nps-expressions-outside-the-console-editor/#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": "Preserve long NPS expressions outside the console editor" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 201, "timeRequired": "PT1M", "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": "Use Regular Expressions in NPS", "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-crp-reg-expressions" } } ] } }