Trevor Vaughan

04 February 2018


fossfeb, open source

Nick Markowski

12 January 2018

If you’ve ever had to work in an IT shop bound by regulations and policies, you know how much of a hassle it can be to integrate new infrastructure and application components, while maintaining a compliant posture.

simp, compliance engine, automation, security, inspec

Russ Holmes

04 January 2018

2018 has barely begun and we’ve already been hit with significant bad news about cyber vulnerabilities. Among others already disclosed during the new calendar year, both Intel and VMware have announced that major cyber flaws have been discovered in their products. And, of course, attempts to fix these issues are having negative impacts on some common anti-virus products.

This is certainly not unique to these tech giants since barely a week goes by without some significant cybersecurity flaw or breach being uncovered. It’s safe to say that these disturbing reports will not be coming to an end anytime soon.

Although it may sometimes feel like it, this doesn’t mean that we should all throw our hands up about how hopeless the cybersecurity situation has become. We can only play the hands we’ve been dealt, and that requires continued efforts at locking down our systems with the many powerful tools we have at our disposal.

Cyber Hygiene Best Practices

Whichever tools you determine are appropriate for your security needs, none will be effective unless one first follows sound cyber hygiene practices. Among the most important of these is ensuring your underlying system adheres to the latest security best practices and is, at the very least, compliant with industry standards and government cybersecurity regulations. Breaches that are advanced by either willful or negligent disregard for these universally acknowledged best practices can be hard to explain – or forgive.

While best practice “table stakes” can be overwhelmingly voluminous and complex to implement and maintain, one does not have to go it alone. In many cases, it’s now possible to transition an existing DevOps platform to a best practices DevSecOps approach, then maintain systems compliance via automated self-healing Continuous Diagnostics and Mitigation (CDM) routines.

Open Source Help

A powerful Open Source offering now available to help address this is known as SIMP (Systems Integrity Management Platform). SIMP was originally developed within the US Intelligence Community to enhance their own ATO (Authority to Operate, federal-speak for C&A) and compliance efforts and is now available for anyone to leverage via GitHub. It only seems fair that we can take advantage of SIMP since it was our tax dollars that funded its development!

Currently riding on the open source DevOps automation technology known as Puppet, SIMP continually scans an environment (in either a development and/or production phase) and provides current system status against a range of cybersecurity benchmarks. Among these are NIST 800-53, NIST 800-171, FIPS 140-2, HIPAA, SOX, PCI-DSS, DISA STIG and others. SIMP can operate within either an on-prem and/or cloud environment and, should a vulnerability be found, can automatically apply remediation actions to immediately correct the flaw, or simply report this information back for further study and action.

With SIMP’s ability to enhance the C&A process, as well as help ensure systems remain compliant once deployed, an organization’s human IT assets can confidently turn their focus to other urgent cyber issues that require attention.

For more information on this Open Source tool, visit the SIMP project website at, or download it at

simp, compliance, automation, security

Trevor Vaughan

17 December 2017

In the course of developing and testing various components for working with Puppet, I had a particularly difficult time with stubbing calls to other Ruby objects outside of my control.

After a ridiculous amount of searching, I finally found the answer that made the whole process seamless.

ruby, mocha, testing, stub

Trevor Vaughan

10 December 2017

The Problem

While creating a custom type for cleaning up stunnel::instance artifacts on the system, I needed to get a list of services that were running on the current host.

This is also something that the svckill native type requires, and was implemented manually in the past, so I thought that there had to be a more reusable method built into Puppet.

programming, puppet, ruby

We work with these Technologies + Partners