Skip to main navigation Skip to search Skip to main content

Security guidelines: Requirements engineering for verifying code quality

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › peer-review

4 Citations (Scopus)

Abstract

The development and delivery of secure software is a challenging task, that gets even harder when the developer tries to adhere to both application and organization-specific security requirements translated into security guidelines. These guidelines serve as best practices or recommendations that help reduce application exposure to vulnerabilities, and provide hints about the application's adherence to high-level and abstract security requirements. In this paper, we present guidelines we gathered from different sources, and we highlight the main issues related to the interpretation and application of those guidelines. We present a first attempt to classify the requirements with the objective of identifying the analysis that should be performed to verify the adherence of the developed software to each of the categories.

Original languageEnglish
Title of host publicationProceedings - 2016 IEEE 24th International Requirements Engineering Conference Workshops, REW 2016
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages80-85
Number of pages6
ISBN (Electronic)9781509036943
DOIs
Publication statusPublished - 12 Jan 2017
Event24th IEEE International Requirements Engineering Conference Workshops, REW 2016 - Beijing, China
Duration: 12 Sept 2016 → 16 Sept 2016

Publication series

NameProceedings - 2016 IEEE 24th International Requirements Engineering Conference Workshops, REW 2016

Conference

Conference24th IEEE International Requirements Engineering Conference Workshops, REW 2016
Country/TerritoryChina
CityBeijing
Period12/09/16 → 16/09/16

Keywords

  • Development Lifecycle
  • Information flow
  • Security Guidelines

Fingerprint

Dive into the research topics of 'Security guidelines: Requirements engineering for verifying code quality'. Together they form a unique fingerprint.

Cite this