SDLC, Agile SDLC og Secure SDLC
SDLC
SDLC: Sikkerhed integreret i agil implementering og softwareudvikling
I takt med den stigende efterspørgsel efter sikre softwareløsninger og øget fokus på cybersikkerhed bliver integrering af sikkerhedsprincipper i etablerede softwareudviklingsmetodikker – som bl.a. agil systemudvikling – stadig mere relevant for organisationer, der udvikler digitale produkter og softwarebaserede tjenester.
Agile udviklingsmetoder og principperne for sikker softwareudvikling, herunder Secure Software Development Lifecycle (Secure SDLC), opfattes ofte som separate tilgange til softwareudvikling. I praksis kan de imidlertid integreres og understøtte hinanden som en samlet ramme for udvikling af sikre softwareløsninger og robust softwarearkitektur. Se hvad vi tilbyder af Secure SDLC rådgivning her.
By integrating security principles into agile processes, security, risk assessment, vulnerability management, and compliance can be incorporated continuously throughout the development process. Secure SDLC thus becomes not a subsequent control step in software development, but an integral part of the analysis, design, development, testing, and implementation of software.
Agil implementering er derfor fuldt kompatibel med sikker softwareudvikling og kan understøtte en systematisk og dokumenterbar tilgang til udvikling af sikre softwareløsninger og digitale produkter.
SDLC
Software Development Life Cycle (SDLC) er en trinvis proces der bruges ved udvikling af softwareløsninger og softwareprodukter. Typisk indebærer processen forskellige faser fra den indledende udviklingsfase og analyse af kravspecifikationer til den efterfølgende udvikling og implementering af software. Processen er med til at sikre et højt niveau af integritet, kvalitet og sikkerhed i softwareproduktet. Secure Software Development Life Cycle (Secure SDLC) er en sikkerhedsorienteret version af SDLC, der hjælper udviklere og organisationer med at gøre deres softwareprodukter mere sikre og robuste over for cybertrusler.
Agile SDLC
Agile SDLC is an iterative and incremental methodology in software development. This variant of the SDLC model prioritizes flexibility, collaboration, and feedback from the customer or product owner throughout the development process. The agile SDLC variant divides development into smaller incremental iterations, e.g., project requirements, architecture and design, as well as development, testing, and feedback.
The most important thing is to ensure the four basic elements of the agile manifesto: early customer involvement, iterative development, self-organizing teams, and an adaptive approach to changes in the project. Like many other development models, the agile SDLC model is also divided into several different phases, including the following.
- Indhentning af krav
Requirements are gathered in collaboration with the customer, with the aim of identifying the business value that the project is to create, so that requirements and functions can be prioritized accordingly. User stories and workshops are typically used to ensure effective dialogue about requirements and needs between the customer and the development team. This process also helps to ensure that the software solution supports both business objectives and technical requirements.
- Design af krav
Once the customer's requirements have been mapped out, they must be converted into practical tasks that can be implemented in the project. One way to make extensive customer requirements more tangible is to divide the tasks into smaller subtasks. Typically, developers will create visual presentations of their solutions to give the customer better insight into the development team's ideas; wireframes and prototypes are often used here to obtain additional feedback for the project and for the system design.
- Kodning
Kode-fasen opdeles i såkaldte sprints, som er mindre, fokuserede udviklingsperioder på ca. en til to uger. Formålet med de enkelte sprints er at levere mindre funktionelle dele af softwareprojektet. Typisk vil udviklingsteamet løbende integrere koden i projektet og så tidligt som muligt identificere og fikse fejl i koden, inden den integreres fuldt ud i softwareløsningen.
- Test af kode
Code testing is an important part of each iteration, ensuring the quality, functionality, and stability of the software. Unit tests are typically used to verify that the individual components of the system work together as intended. The development team then conducts end-user tests, where users are allowed to interact with the software to ensure that it meets the customer's requirements for the product and provides the desired functionality.
- Udgivelse af kode
Code release is largely about delivering functionality to the product. This typically involves the use of automated tools and CI/CD processes that enable fast and consistent software releases. It is important to monitor the release process, as this allows errors to be identified and corrected quickly.
- Feedback fra kunder
Feedback is an essential step in improving the product and in the ongoing development of the software solution. Customers and end users can send their feedback through either a questionnaire, direct communication, or analysis of product usage. This feedback is used to refine requirements, identify shortcomings, and prioritize changes in future iterations of the system.
Secure SDLC (SSDLC)
Secure SDLC largely follows the standard development model, where the project is divided into phases such as requirements, design, development, verification/testing, maintenance, and improvement of the software product.
Secure SDLC aims to reduce the risk of data leaks, increase the resilience of applications, strengthen cybersecurity, and increase user confidence in software products, while reducing the potential costs following a security incident.
The process follows the initiative known as "shift-left," which focuses on implementing security as early as possible in the software development process. If the development team is responsible for designing and implementing security measures, they can deal with security issues more quickly, as they also have ownership of the code. This often leads to higher quality software applications and better security.
Ved at fikse fejl og mangler så tidligt i projektet som muligt kan omkostningerne reduceres markant. Tal fra IBM viser, at det i nogle tilfælde kan koste op til hundrede gange så meget at fikse problemer i produktionen, som hvis de var blevet håndteret i designfasen. Tidlig håndtering af problemerne kræver dog et godt overblik over projektets omfang. (IBM System Science Institute: Relative Cost of Fixing Defects, 2010).
Læs mere om faserne i en Secure SDLC-proces her.
SBOM ift. NIS2, ISO 27001, AI Act og CRA
1) SBOM generelt
Moderne software består sjældent af kode udelukkende udviklet internt i organisationen. Mange systemer og softwareprodukter består i dag af en kombination af internt udviklet software, open source komponenter og tredjepartsbiblioteker. Denne kompleksitet i moderne softwareudvikling skaber udfordringer i forhold til cybersikkerhed, håndtering af sårbarheder, software supply chain security og overholdelse af regulatoriske krav og compliance.
A Software Bill of Materials (SBOM) is a structured list of all components, libraries, and dependencies in a software product. An SBOM acts as an ingredient list for software, enabling organizations to identify, analyze, and manage vulnerabilities in their software products and create greater transparency in the software supply chain.
SBOM has become a key tool in software supply chain security, especially after a series of major cybersecurity incidents such as the SolarWinds attack and the Log4Shell vulnerability. During these incidents, organizations often had difficulty quickly identifying exactly which systems contained the vulnerable components.
Several cybersecurity standards and regulatory frameworks have therefore begun to address the need for greater visibility in software products and software components. In the EU context, SBOM is particularly relevant in relation to the NIS2 Directive, ISO 27001, the AI Act, and the Cyber Resilience Act (CRA). Although the requirements vary between these frameworks, SBOM plays a central role in risk management, software supply chain security, and vulnerability management.
2) SBOM i NIS2
The NIS2 Directive aims to improve cybersecurity in critical and important sectors in the EU. The directive sets requirements for organizations' risk management, supply chain security, and how organizations handle vulnerabilities and cybersecurity risks in their IT systems and digital services.
NIS2 does not explicitly require the implementation of an SBOM. However, an SBOM can support several of the directive's security measures and help organizations achieve and maintain a high level of cybersecurity in their software solutions and digital systems.
Læs mere om vores NIS2 rådgivning her.
Relevant NIS2 requirements
NIS2 artikel 21 beskriver en række cybersikkerhedsforanstaltninger som organisationer skal implementere, herunder risikostyring, leverandørkædesikkerhed, sårbarhedshåndtering og beredskabsplaner. En SBOM kan hjælpe med at understøtte disse krav ved at give organisationen et detaljeret overblik over softwarekomponenterne i et system og deres afhængigheder i softwareleverandørkæden. Få overblik over kravene og guide til NIS2 implementering i jeres organisation her.
SBOM i praksis under NIS2
- Leverandørkædesikkerhed
SBOM giver organisationer mulighed for at identificere hvilke tredjepartsbiblioteker og softwarekomponenter der indgår i et system. Dette gør det muligt at vurdere risikoen ved tredjepartssoftware, identificere komponenter fra usikre leverandører og dokumentere softwareafhængigheder i leverandørkæden.
- Hurtigere sårbarhedshåndtering
Når en ny sårbarhed offentliggøres, for eksempel via CVE-databasen, kan organisationer bruge deres SBOM til hurtigt at identificere om der findes sårbare komponenter i deres systemer. En SBOM reducerer den tid der bruges på at identificere påvirkede systemer, understøtter en rettidig risikovurdering og gør patch management, vedligeholdelse og dokumentation mere effektiv.
- Beredskabsplanlægning
SBOM kan også understøtte organisationens beredskabsplan ved at give et klart overblik over hvilke komponenter der er til stede i et eventuelt kompromitteret system. Dette gør det lettere for organisationer og myndigheder at analysere angrebsvektorer i forbindelse med en sikkerhedshændelse og identificere kompromitterede komponenter.
3) SBOM i ISO 27001
Overordnet perspektiv
ISO 27001 is an international standard for an information security management system, also known as an Information Security Management System (ISMS). The standard focuses primarily on management processes and organizational controls rather than specific technical solutions. ISO 27001 therefore does not directly require the implementation of an SBOM in the organization, but an SBOM can be a powerful tool to support several of the standard's controls within cybersecurity and software management.
Læs mere om vores ISO 27001 rådgivning her.
Relevant controls
SBOM can particularly help support the following controls in ISO 27001 Annex A.
- Forvaltning af aktiver
Organizations must identify and register information assets. Software components and dependencies can be considered digital assets, where an SBOM can serve as a detailed record and documentation of software assets in the organization's systems.
- Secure Software Development Life Cycle
ISO 27001 stiller krav til sikkerhed i udviklingsprocesser. Her kan SBOM med fordel integreres i Secure Software Development Lifecycle (SSDLC). Dette kan f.eks. ske gennem automatiseret generering af SBOM i CI/CD-pipelines som dokumentation for softwarekomponenter i et system. En automatiseret SBOM i CI/CD-processer kan mindske tidsforbruget og samtidig understøtte scanning af de komponenter der tilføjes, herunder open source komponenter, så organisationen får et bedre overblik over softwarekomponenternes afhængigheder.
- Vulnerability management
En SBOM understøtter sårbarhedshåndtering fordi den kan bruges til at identificere hvilke systemer der er påvirket af kendte sårbarheder. Dette gør det muligt at prioritere patching og sikkerhedsopdateringer baseret på eksponeringen af softwarekomponenter.
- SBOM som del af ISMS
I et ISO 27001-baseret ISMS kan SBOM integreres i flere centrale processer, blandt andet forvaltning af aktiver, risikostyring, leverandørkædesikkerhed og sårbarhedshåndtering. SBOM fungerer dermed som et værktøj til at gøre flere af standardens kontroller mere operationelle og praktisk anvendelige i organisationens cybersikkerhedsarbejde. Få overblik over et typisk forløb mod ISO 27001-certificering her.
4) SBOM i AI Act
The AI Act regulates the development and use of artificial intelligence in the EU. The regulation focuses in particular on transparency in AI systems, risk management, security, and documentation. For high-risk AI systems, the AI Act requires comprehensive technical documentation.
Læs mere om vores rådgivning inden for AI Act her.
The role of SBOM in AI systems
AI systems often consist of a complex software stack that typically includes machine learning frameworks and open source libraries, among other things. An SBOM can help organizations document these software components and create transparency in the software architecture that underpins the AI system.
Relevance for compliance in the AI Act
En SBOM kan særligt hjælpe med at understøtte kravene om dokumentation af softwarekomponenter i AI-systemer og skabe gennemsigtighed i softwareleverandørkæden. Samtidig kan en SBOM understøtte organisationens sikkerhedsvurderinger og risikostyring. Dette kan være særligt relevant for organisationer der udvikler eller arbejder med high-risk AI-systemer. Læs mere om hvordan din organisation bliver compliant med AI Act her.
5) SBOM i Cyber Resilience Act (CRA)
The Cyber Resilience Act is an EU regulation that sets requirements for cybersecurity in products with digital elements. The CRA therefore applies to software products, hardware with software, IoT devices, operating systems, applications, and other digital products.
The CRA places great emphasis on software supply chain security, as manufacturers and suppliers of products with digital elements must be able to guarantee the security of the products they sell within the EU.
Læs mere om vores rådgivning inden for Cyber Resilience Act her.
SBOM requirements in CRA
The CRA requires manufacturers to document the software components included in their products. In practice, this often means that a Software Bill of Materials is necessary for compliance. An SBOM can therefore be used to document software components, open source dependencies, and third-party libraries, as well as to manage vulnerabilities in the software supply chain.
Vulnerability management
CRA kræver også at producenter etablerer processer for overvågning af sårbarheder i deres softwareprodukter, så sårbarheder kan håndteres så hurtigt som muligt og ikke udgør en unødig risiko for brugerne af produktet. Der stilles samtidig krav til rapportering af sikkerhedsproblemer, så relevante parter og myndigheder kan informeres om sikkerhedsbrister i produkter. CRA kræver desuden at sikkerhedsopdateringer udgives gennem hele produktets levetid, og derfor skal producenter sørge for løbende sårbarhedsvurderinger og sikkerhedsopdateringer for at opretholde produktets sikkerhedsniveau. Læs mere om hvordan din organisation bliver compliant med CRA her.
Få hjælp til at etablere Secure SDLC
Nesp.ONE hjælper med at vurdere den nuværende udviklingspraksis og etablere en Secure SDLC-proces, der passer til organisationens risici, systemer og arbejdsform.
Se vores rådgivning om Secure SDLC
Se vores kursus i Secure SDLC
Ready to strengthen your cybersecurity?
Eller har I spørgsmål som ikke blev besvaret. Bestil en 15 min gratis gennemgang med en cybersikkerhedsekspert.