With the release of build.cfengine.com, I have been working to migrate some of our own security related policy into modules of their own. CFEngine Build and the cfbs tooling allows us to organize policy into modules, which are easy to update independently and share with other users. Let’s take the scenic route and look at what life is like with cfbs. One of our security policies requires that the password hashing algorithm in /etc/login.defs is set to SHA512.
Have you ever wondered how a site was designed and how the ideas were conceptualized into a webpage? If your answer is yes, you are in the right place! In this post, I will show you our journey to create our latest web page, CFEngine Build. From start to finish, how did we do the design and make the design decisions? So without further delay, let’s jump straight in!
Nowadays, staff in organizations are required to access multiple applications in their infrastructure. This can lead to the user having to manage multiple login credentials and passwords. There are many solutions available that provide a single sign-on (SSO) capability — such as Okta, LDAP, and Active Directory — which is becoming common practice across businesses.
The world has changed since I started out on a help desk in Colorado 25 years ago. In those long ago years, a company’s desktop machines actually lived under the desks of many in the organization (and often doubled as a foot warmer!) and configuration was done machine by machine manually, or maybe even by some script that was created to run at login if we were lucky. If there were laptops in use by the business users, they were a lot less mobile and rarer than in today’s business world...
Nearly two-thirds of IT executives say they plan to implement automation technology within the next year and a half. Despite this ambitious goal, however, 50% of those IT leaders admit that a lack of automation skillsets is currently hindering their progress. As the demand on IT infrastructures continues to grow at an astronomical rate, an epic increase in complexity has inevitably followed.
As ITSM thought leader and consultant Doug Tedder has said, “Automate the obvious.” So what’s obvious? We shouldn’t have to think very long…
