I would advice all developers to read the Apple TN2459 concerning KEXT Consent.
https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658
This will impact your work and your users, even if your app does not use KEXTs.
You can add to the trusted developer team list for KEXT-CONSENT by booting to Recovery and using spctl as described in the note. If the KEXT you are trying to load is not yours, you need to ascertain the TEAM ID of the kext by using codesign. It is not clear in the note, but the team ID is not the company string as reported in the dialog, but the HEX key in the certificate and also used for siging in Xcode.
I prefer to run with SIP enabled, but I think that the current apporach will have the effect that a lot do support people will advice their users to turn off sip, which is arguably and easier command then trying to have them type in a complex string like "spctl kext-consent allow XYZABCD3FT."
I have been working on this issue for several days to understand all the implications. We have a non-technical user base and require a KEXT, the impact will be horrific.
No more ease-of-use and plug-n-play on macOS... It is now a sad state that our app will be easier on Windows 10!