Related Content
 |
Signs of a Project Headed for Trouble Projects rarely get in trouble suddenly. More often, the descent into trouble is gradual, and the signs are easy to miss—but they are there. If you detect any of these potential signs of possible failure, it would be wise to take steps sooner rather than later to address them and get the project back on track. |
|
 |
5 Features of a Successful DevSecOps Pipeline When practicing DevOps, how should you include security? What's the best way to build security into an existing continuous integration, continuous delivery, and continuous deployment pipeline? Let’s take a look at five essential features of successful DevSecOps pipelines and analyze where security can benefit most. |
|
 |
Georgia Tech IoT Study: Takeaways for Smart Cities The internet of things has sky-high expectations, and smart cities, where devices connect across public and private sectors, is one of the drivers fueling the fervor. But there are also skeptics saying the IoT is slow to materialize, which poses questions about risks surrounding cyber security and privacy. |
|
 |
5 Myths about API Security APIs are designed to provide interfaces between multiple applications, allowing them to work together. From a security perspective, this is a powerful tool to have. Unfortunately, the effectiveness of APIs diminishes if they are misunderstood. Here are five common myths about API security, along with the facts. |
|
 |
The Blurred Lines between the Open Source and Closed Source Worlds The open source and closed sourced worlds need each other—not only for healthy competition, but more importantly, for healthy collaboration, too. Mukesh Sharma looks at recent collaborative efforts between the open source and closed source communities and what is driving these changes. |
|
 |
The Risk of Overemphasizing Risks We are trained to identify and evaluate risks. This prevents teams from making decisions that are unlikely to work, saving time and money and helping the team move forward. However, a risk-avoidance mindset can also stop progress. Successful agile teams see risks as ways of starting a conversation, not stopping it. |
|
 |
A Checklist for Managing Go-Live Decisions and Risks If you have to replace a complex existing data system in production, decisions about when and whether to go live should be treated with gravity and care. One process that can help keep you honest is developing checklists that describe very clearly what is expected to be accomplished and verified at each milestone. |
|
 |
A Definition of Done for DevSecOps In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to produce a viable candidate for production, so we have to look at many different aspects of quality, including security. To be sure we hit all the crucial marks, we should have a definition of done for DevSecOps. |
