getCert is Open Source!

We have a very special announcement this month. We are making getCert – SSL Certificate Discovery open source and free to use. The code is available at GitHub (Traversys getCert CE) under the Apache 2.0 software license.

We hope that by making it open source, there will be more adoption and more importantly, the opportunity for others to contribute improvements.

The development environment currently runs on a CentOS docker instance, or you can download the binary for immediate install on an on-premise appliance.

Additional support can be provided on a work order basis, feel free to get in touch –

TPL Crash Course – March Discount

With the current uncertainty around Coronavirus and having to self-isolate or find things to do during quarantine, there’s no better time to pick up a new skill – particularly if you are a Discovery Administrator who is looking to get to grips with TPL.

Just to entice you, we’ve got another time-limited discount special!

Get the TPL Crash Course for BMC Discovery now for $99.99 – valid for the next 5 days until 22nd March 2020!


TPL Crash Course for BMC Discovery on Udemy

SSL Certificate Discovery Reaches 1.0

Traversys are proud to announce that we have updated our SSL Certificate extension for BCM Discovery to include an automatic installer, with dashboards and reports.

Our SSL Certificate Extension can provide insight into:

  • Signing status (self-signed or Certificate Authority)
  • Certificate Lifecycle
  • Serial Numbers
  • Encryption Level

Certificate capture works independently of the Discovery scan, meaning certificates can also be captured for servers that are not part of targeted scanning.

Supports versions 10.2 – 11.3 if BMC Discovery.

Talk to us today about enabling this for your Discovery solution.

Automating The Department of Redundancy Department

This post was first published by Wes Fitzpatrick on LinkedIn (19th Feb 2015). It has been edited and updated.

In recent times I’ve had the privilege to sit in on client meetings with small businesses who are moving from paper-based system to a partially or fully automated ITSM process.

It’s a great boost to see a customer who is excited by the reduced time, reduced cost and efficiency that a new system is going to bring – especially when you are the one who is going bringing it to them! It’s where you can immediately see the benefits of introducing ITIL to a system where it is only vaguely understood. Something that you can often lose sight of working in well-established larger organisations.

That said, it never ceases to amaze me during scoping exercises how often a customer wants to replicate the the paper system in the automated one.

Working with a product like Ivanti’s Cloud ITSM or ServiceAide, customisation is not a problem – there’s very little you can’t do to customise it to your own processes, however one of the questions that should be asked before blindly accepting requirements is why?

In Change Management for example, a paper-based process might require 3 different sign-off’s which is an easy trap for an executive to translate as 3 additional approval stages that need to be added to the automated system. But if the automated system allows you set up a CAB, notify all 3 people at once, set the approval rates – there may really be only one approval stage needed. In such examples, I’ve seen far too many situations where 3 stages have been created, rather than trying to help the customer to realise the benefits of automation.

The danger by trying to replicate as much as the paper-system as possible – you’re potentially cancelling out the benefits and efficiency the system brings.

It’s important to look at your current process and question what are the intended outcomes, particularly in light of the objectives behind automation. Rather than look at things from your processes to introduce to automation, try to look for things that automation can help you leave behind.