Operations | Monitoring | ITSM | DevOps | Cloud

Auvik Use Case #6: Identifying Vulnerable Devices From Vendor Recalls and Security Notices

When network hardware vendors issue device recalls, field notices, or security alerts, the implication can be massive for MSPs. Take the 2017 clock signal issue, for example. That huge recall of Intel microchips was a large-scale vulnerability for tons of devices—and meant MSPs had to figure out which devices were affected on which client sites.

An Organized Workflow for Prototyping

In the world of agile there’s a demand to solve grey areas throughout the design process at lightning speed. Prototypes help the scrum team test ideas and refine them. Without prototypes, we can’t test ideas until the feature or product has been built which can be a recipe for disaster. It’s like running a marathon without training.

The Seven Digital Sins Of IT-Business Disconnect

There’s a disconnect between business leaders and IT. As noted by a 2017 Forrester study conducted on behalf of Nexthink, just 36% of business users “think IT is aligned with the needs of the business,” even though technology services are now embedded into every aspect of enterprise culture, from mobile device use to wifi access to cloud computing.

GitHub Actions: Automating Serverless Deployments

The whole internet is abuzz over GitHub Actions, if by ‘whole internet’ you mean ‘the part of the internet that is obsessed with serverless ops’ and by ‘abuzz’ you mean ‘aware of‘. But Actions are a bit surprising! GitHub is a company that has famously focused on doing a single thing extremely well. As the ranks of developer-tooling SaaS companies swells by the day, you would think GitHub would have long ago joined the fray.

Three high level patterns in CFEngine

How do you deal with config files that need different settings based on various services that are running on a host and cooperate with other teams? It’s a common question, and it came up on in #cfengine on irc.freenode.net recently. The issue is that team A might be working on package A, which requires some environment variables set. But team B might be working on a totally different thing — and want to achieve the same thing.

CloudFormation Stack Drift Report Action

Last week, AWS announced a fantastic new feature for AWS CloudFormation, CloudFormation Drift Detection. Drift detection allows you to determine whether the AWS resources controlled by your CloudFormation stacks have drifted from their original configuration. This can happen if you manually adjust properties of your AWS resources. Today, we’re excited to announce a new action to report on your CloudFormation drifted stacks: CloudFormation Stack Drift Report.