2016 · 11 citations · 0 references
ComputingComputer ScienceRisk ManagementComputer SecurityRegulatory ComplianceSoftware EngineeringCompliance AssuranceCompliance RequirementsCybersecurity ComplianceSecure Requirements EngineeringSoftware Quality AssuranceSoftware Security EngineeringCompliance Requirements AnalysisCompliance Requirements ManagementDevopsRequirements ComplianceSecurity Standards ComplianceSoftware Development LifecycleSoftware Development MethodologySoftware Process Compliance
Compliance and regulation are fundamentally intended to establish trust between entities that create and use shared computing systems across all layers. Security compliance requirements (such as those of Payment Card Industry (PCI) Data Security Standard (DSS) <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">1</sup> or the US NIST 800 special publication series <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">2</sup> ) are framed around a classic “Waterfall” software development methodology. The software industries recent shift to a “DevOps” methodology has put the trust created with compliance at risk. This paper contains a proposed strategy to achieve compliance and establish trust using a DevOps environment.