This kit is compatible with any DotNet Core application (currently V8.0 & later) including Winforms, WFP & console applications.
For the majority of drivers, however, the recommended host should be a console application. In recent years, we have noted that customer infosec teams are increasingly uncomfortable with the notion of drivers, which are essentially server applications, requiring to be run in a logged in Windows desktop session. In version 5.5, other essential components of BNCS, such as CSI, will still require a logged in Windows desktop with BNCS Workstation Manager.
In BNCS v5.5, we recommend that drivers, including those developed with this DDK, are also run from the Workstation Manager. However, we strongly encourage developers to build their drivers as console applications with web based UI’s.
In BNCS V6.0, drivers can be containerised using Docker or similar. This transition will be significantly easier for drivers that are implemented as console applications. To facilitate this transition in V6.0, the DDK will be updated with a built-in, dotnet native implementation of CSI & the XDS protocol optionally enabling a driver to run & interact directly with the BNCS network without the need for an out-of-process CSI.
The current & future structures is demonstrated by the following diagram:
Obviously, user interaction and monitoring of an application without a desktop UI changes and drivers developed with this kit generate a web based user interface by default which can be modified to provide driver specific functionality if required. Please refer to the later chapter for information on this.