Here are the articles, videos, and tools that we’ve been excited about this October. We hope you enjoy these links, and we look forward to hearing what you’ve been reading in the comments or on the Interrupt Slack.
In the first part, I outlined some of the terms associated with the delivery of IoT. Next, let’s look at how this gets complex. You will need to read the state of each sensor (through their appropriate API and through their appropriate vendor-supplied hub), create logic to determine what actions must be taken when certain conditions are met, and then deliver these as a workflow to each responder, and confirm through data collected from sensors that the requested change was implemented.
In this blog post, I will be talking about label standard and best practices for Kubernetes security. This is a common area where I see organizations struggle to define the set of labels required to meet their security requirements. My advice is to always start with a hierarchical security design that is capable of achieving your enterprise security and compliance requirements, then define your label standard in alignment with your design.
