Runtime security for Rancher environments requires putting controls in place to detect unexpected behavior that could be malicious or anomalous. Even with processes in place for vulnerability scanning and implementing pod security policies and network policies in Rancher, not every risk will be addressed. You still need mechanisms to confirm these security barriers are effective and provide a last line of defense when they fail.
Docker is an essential bridge in modern DevOps. Despite Kubernetes overtaking Docker on orchestrating containers, the Docker container itself remains the standard and likely will for the foreseeable future. We developed the Docker Metrics collector to operate as its own container that will run Metricbeat using the modules you are running in real time. Now, in addition to the Docker module, we are now releasing an AWS module for operations in the cloud.
In our previous announcement for the removal of the Codefresh Docker registry, we presented a timeline of the migration phases along with the actions expected from our customers. One of the milestones in the migration process is the introduction of our new Image API along with several enhancements on the pipeline build step. We believe that these features deserve a dedicated explanation of why they are useful on their own (regardless of the registry removal).
Offering help in a crisis is a positive way to maintain communication and build a strong business relationship that may pay dividends down the road.
This is a repost from the JFrog dev.io blog site. When you’re new to an industry, you encounter a lot of new concepts. This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers. In this series, I’ll cover tools and terminology common to the DevOps space, plus the occasional newbie-friendly tutorial for emerging or established technologies. If you have a request or suggestion, let me know!
Many organizations are prioritizing the health and well being of their workforce in the wake of the current global pandemic. Many threat actors are also taking advantage of this opportunity. I’ve seen recent examples of social engineering—with calculated phishing campaigns preying on those who seek information on the COVID-19. As noted by Security Researcher Brian Krebs, one hacker group even used a copy of a legitimate map of the impact of the virus to infect machines with malware.
As federal, state, and local government agencies scramble to create emergency response processes and procedures, be advised that IT service management (ITSM) can play a critical role in supporting emergency response plans and associated processes. Government and commercial business emergency response plans define how agencies and commercial organizations respond to catastrophic events in the environment.
A Network Operations Center (NOC) is a location from which IT support technicians can supervise, monitor, and maintain client networks and infrastructure. Because they act as a central nervous system for many organizations, NOCs are typically located in a central physical location. The global coronavirus (COVID-19) pandemic is an unprecedented situation that is creating new challenges for everyone—and that includes NOCs.
A few months ago, Honeycomb released our SLO — Service Level Objective — feature to the world. We’ve written before about how to use it and some of the use scenarios. Today, I’d like to say a little more about how the feature has evolved, and what we did in the process of creating it. (Some of these notes are based on my talk, “Pitfalls in Measuring SLOs;” you can find the slides to that talk here, or view the video on our Honeycomb Talks page).
