In the last decade, companies adopted DevOps as a fast path to deliver software products according to customer expectations, with well aligned teams and in continuous cycles. As a basic practice, DevOps relies on pipelines that simulate factory swim-lanes. The more automation in the pipeline, the shorter a lead time is supposed to be. However, applying DevOps is challenging, particularly for industrial control systems (ICS) that support critical infrastructures and that must obey to rigorous requirements from security regulations and standards. Current research on security compliant DevOps presents open gaps for this particular domain and in general for systematic application of security standards. In this paper, we present a systematic approach to integrate standard-based security activities into DevOps pipelines and highlight their automation potential. Our intention is to share our experiences and help practitioners to overcome the trade-off between adding security activities into the development process and keeping a short lead time. We conducted an evaluation of our approach at a large industrial company considering the IEC 62443-4-1 security standard that regulates ICS. The results strengthen our confidence in the usefulness of our approach and artefacts, and in that they can support practitioners to achieve security compliance while preserving agility including short lead times.
翻译:在过去的十年中,公司采用DevOps作为按照客户期望提供软件产品的捷径,其团队协调良好,周期性持续。作为基本做法,DevOps依靠模拟工厂游泳线路的管道。管道自动化程度越高,准备时间就越短。然而,应用DevOps具有挑战性,特别是对支持关键基础设施和必须遵守安全条例和标准的严格要求的工业控制系统(ICS)而言。目前关于遵守安全规则的DevOps的研究为这一特定领域以及系统应用安全标准提供了未加填补的空白。在本文件中,我们提出了一个系统化的方法,将基于标准的安保活动纳入DevOps管道,并突出其自动化潜力。我们的意图是分享我们的经验,帮助从业人员克服在发展过程中增加安全活动与缩短准备时间之间的权衡问题。我们考虑到监管ICS的IEC 62443-4-1安全标准,在一家大型工业公司中评估了我们的方法。结果加强了我们对我们方法和工艺品的使用的信心,从而可以支持从业人员实现安全合规,包括保持短期领导时间。