Recording Certificates as Assets - Fields required

[samwoo]

Good afternoon,

It would be good if we can record certificates as Assets and then be able to link them as CI's to other assets, but I don't have a great deal of knowledge on how certificates work or are set up / issued.

But I think we need either a new asset class, or extra fields adding to existing classes... (an expert can say whether these are important or not, or whether we need more fields added)

• Friendly Name
• Issued To [Text]
• Issued By [Text]
• Issued Date [Date]
• Start Date / Valid from [Date]
• Expiry Date / Valid to [Date]
• Certificate Type (Wildcard, Single Domain) [List]
• Certificate Store (Personal, Trusted Root Certification, Enterprise Trust etc...) [List]
• Certificate Template
• Thumbprint [Text]
• Intended Purpose(s) [Multiline Text - displays Wiki Markup in read only mode]
• Purchase Cost
• Certificate Path

I don't want to muck around with translating the existing fields used for other Asset Classes and Types.

With this information, we can then run automation to log tickets when certain certificates are due to expire etc. and have everything updated as part of the Business Process.

Please can this be considered.

Kind Regards,

Samuel

[samwoo]

Good morning,

I was wondering if this has been picked up and discussed at all? We've had some certificates we were not aware of expiring last minute and need somewhere to record this information where we can interact / run reports from with ease and eventually use it to auto log tickets (hopefully automatically) in the future.

Thanks,

Samuel

[samwoo]

Good afternoon,

Happy New Year  

I was wondering if this has been looked at by any chance or have I posted this in the wrong forum?

Thanks,

Samuel

 

[Steve Giller]

Currently adding Certificates as Assets is not being considered, these would be considered more like a type of Document than an Asset, possibly creating a 'certificate' document template in Document Manager, and using tags and categories to organise them with links to assets and requests would be a way forward on this.

[samwoo]

Thanks @Steve Giller 

I just wanted to make sure there hasn't been any confusion in what I have requested:

1) I'm talking about System Certificates which needs to be managed, that expires over a period of time etc. for example, Wildcard certificates, SSL certificates etc.
2) I'm not talking about certificates that people earn when they complete something.

Since the system certificates are managed entities, this is why I raised the request to have an Asset Class for Certificates or at the very least provide some extra Asset Fields that could be used in an existing Asset Class.

If the developer response is related to 1):
Then please could I request the ability to add Custom Fields to documents, so that way we can use that information to track when system certificates are due to expire etc. or could there be other considerations or possibilities, for example is it possible to report on the contents of a Hornbill document (that isn't an uploaded word document) then we can generate a report on when an certificate is due to expire, so we can regularly check and contact suppliers well in advance.

If it's related to 2):
Then please can you re-check with development on my actual requirements as I am not talking about certificates of completion or any physical document which is what Document Managment would be used for.

Thanks,

Samuel

[Berto2002]

+1 certificate expiry is a massive issue and causes huge downtimes if not managed correctly. Also we required certs to be change controlled so they tick all the boxes to be Assets and I think warrant either their own class. Alternatively, consider a "Virtual" Asset class which also contains things like API tokens, FQDNs, SSO

[samwoo]

I've had to make use of the Software class for this, but I still think an Asset Class for Certificates should be considered? Either that or provide additional fields for the Software class that simply has "Start Date", "End Date", "Expiry Date".

The Software Asset already contains Licence Start Date, Licence End Date and Licence Expiry Date but I don't want to translate these as this is being used for other Software Asset Types.