)
)
)
Summary
Security grew out of IT during the worm era of Code Red and Nimda, but patching and configuration stayed IT's job even though they are security imperatives. Automox CISO and SVP of Product Jason Kikta explains to host Steph Rizzuto why that split shapes the product: Automox is moving from a deferral-based patch model to a deadline-based one, where a patch must be done by a set date and time but the end user chooses when. It is also exposing patch and configuration proof of work through an API so IT can feed those results into external security and compliance tools. Kikta also says core controls like single sign-on, multi-factor authentication, and audit logs should be included, not sold as an upcharge.
)
)
)
