NServiceBus 10.2

Last reviewed Sep 19, 2026

Export as PDF

Prompt Details

Prompt Composition

2prompts
  1. C# 14106 lines · 4.4K tokens
  2. NServiceBus 10.267 lines · 3.3K tokens
Total173 lines · 7.6K tokens

CWE Coverage

  • 20
  • 22
  • 59
  • 78
  • 89
  • 94
  • 117
  • 190
  • 208
  • 209
  • 214
  • 250
  • 257
  • 295
  • 306
  • 319
  • 323
  • 327
  • 338
  • 362
  • 367
  • 378
  • 426
  • 502
  • 532
  • 611
  • 636
  • 639
  • 674
  • 759
  • 770
  • 772
  • 775
  • 778
  • 798
  • 807
  • 829
  • 841
  • 862
  • 863
  • 915
  • 916
  • 918
  • 922
  • 1333
  • 1395

Prompt Preview

Apply the C# 14 prompt first. These rules cover NServiceBus 10.2 on .NET 10, including optional transport, persistence, encryption, and Claim Check integrations when installed.

Runtime, endpoint identity, and routing

  • Require .NET 10 or a later supported runtime; NServiceBus 10 does not run on .NET Framework. Select NServiceBus 10-compatible components and review their advisories independently. These rules cover the 10.2 line and were checked against 10.2.8; track the latest patch of the line rather than freezing dependencies on the release they were checked against.
  • Set EndpointConfiguration names, transport connections, queue addresses, and routing from trusted deployment configuration. Separate production input, error, audit, and subscription resources from development and from unrelated trust domains.
  • Enforce transport authentication, encrypted connections, and endpoint-specific send, receive, and subscription permissions using the selected broker's controls. A component allowed to write an input queue can submit message bodies and headers; queue access does not establish an end-user identity or resource authorization.
  • Configure command destinations with RouteToEndpoint; configure event subscriptions according to the transport's native or message-driven publish/subscribe model. Allowlist destinations passed to SendOptions.SetDestination or RouteToSpecificInstance instead of deriving them from incoming data.
  • Validate the reply destination against the authenticated conversation before sending sensitive data with context.Reply or