Advice around how to manage TLS which is a protocol standard not linked to one publisher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19 hours ago
Hi
We recently turned on implemented SAM Pro/ SAM enterprise, so are cleaning up our software models so that publishers and products are correctly populated to benefit from the Service Now content library; but we have come across an entry that we are not sure what to do with/ about, so thought we would ask the community what other users do to get around this issue (if you also face it)?
We have a software model called TLS 1.0 (pre-dating the swithc on of SAM enterprise) and I have been asked about creating TLS 1.3 by the application owner/ product owner. The problem is that TLS is a protocol standard, so it's not limited to one publisher albeit developed by and maintained by the Internet Engineering Task Force (IETF). It's implemented by software, hardware, and services like web servers (Apache, NGINX), browsers (Chrome, Firefox), operating systems (Microsoft), and security vendors (Cloudflare, Fortinet) that support the standard itself, so its not limited to one publisher and the content library does not pick up any of the word combination I have tried so far to figure out a workaround.
Ideally it would be removed from our software model database, but the owner wants us to retain it whilst adding a new one.
All thoughts, suggestions, recommendations welcome!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Hi @davidwilson ,
I agree with you, TLS is no software to be tracked. Did he share use case/business need with you?
SN also supports certificate management incl. additional details etc., maybe he is looking for such kind of manager.
Best, Dennis
