Upload
qonex
View
76
Download
1
Embed Size (px)
Citation preview
© NEXOR 2016
TRUSTWORTHY SOFTWARE
COLIN ROBBINS
Slides marked “Source: TSI” in the footer are courtesy of:
Ian Bryant, Technical Director of the TSI.
© NEXOR 2016
AGENDA
Summary
Introduction 1
Trustworthiness 2
3
4
Building Trustworthy Software 3
Identifying Trustworthy Software 4
© NEXOR 2016
I WEAR MULTIPLE HATS…
Managing Consultant
QonexTechnical Director
Nexor
Steering Group
Trustworthy Software Initiative
Chairman (East Midlands)
Institute of Information Security
Professionals
© NEXOR 2016
QONEX - OVERVIEW
We help organisations understand cyber security and manage the associated risks.
• Security Management
• Risk treatment
• Audit
• Compliance
• Risk
• Threat
• Vulnerability
• Forums
• Workshops
• Training
Educate Assess
ActReview
© NEXOR 2016
o Enhance the overall software and systems
culture, with the objective that software should
be designed, implemented and maintained in a
trustworthy manner.
TRUSTWORTHY SOFTWARE INITIATIVE
TSI Mission
© NEXOR 2016
AGENDA
Summary
Introduction 1
Trustworthiness 2
3
4
Building Trustworthy Software 3
Identifying Trustworthy Software 4
© NEXOR 2016
TSI DEFINITION OF TRUSTWORTHINESS…
Derived from definition of Dependability
[TSI/2015/047]
© Copyright 2003-2015
Trustworthiness
Safety
The ability of the
system to
operate without
harmful states
Reliability
The ability of the
system to deliver
services as
specified
Availability
The ability of the
system to deliver
services when
requested
Resilience
The ability of the
system to
transform,
renew, and
recover in timely
response to
events
Security
The ability of the
system to remain
protected against
accidental or
deliberate
attacks
Source: TSI
© NEXOR 2016
MAPPING SECURITY AND TRUSTWORTHY
o On their own, each
component has a
methodology
o The challenge is
combining it all
together
Source: TSI
Security
Confidentiality
Safety
ResilienceReliability Availability
Integrity
© NEXOR 2016
“Trustworthy Software is software
that is appropriately free from
defects that cause it to fail.
It performs as it should, when it
should and how it should.”
TSI WORKING DEFINITION…
© NEXOR 2016
AGENDA
Summary
Introduction 1
Trustworthiness 2
3
4
Building Trustworthy Software 3
Identifying Trustworthy Software 4
© NEXOR 2016
Trustworthy
Components
PILLARS OF TRUSTWORTHINESS
[TSI/2015/047]
© Copyright 2003-2015
Trustworthy
Practitioners
Trustworthy
Organisations
Trustworthiness
Instruction
Trustworthy
Software
Source: TSI
© NEXOR 2016
SOFTWARE DEVELOPMENT PROCESSES
Derived from ISO Management Systems Standards
Process OutputInput
Controls
Resources
Objectives
Measures
Technology People
© NEXOR 2016
TRUSTWORTHY SOFTWARE
Trustworthy Software is software that is appropriately free from defects that
cause it to fail. It performs as it should, when it should and how it should.
© NEXOR 2016
o Governance
o Risk
o Controls Personnel
Physical
Procedural
Technical
o Compliance
PAS 754
Software Trustworthiness – Governance and Management – Specification
© NEXOR 2016
o Governance
o Risk
o Controls Personnel
Physical
Procedural
Technical
o Compliance
PAS 754
Software Trustworthiness – Governance and Management – Specification
© NEXOR 2016
SOFTWARE DEVELOPMENT PROCESSES
Derived from ISO Management Systems Standards
Process OutputInput
Controls
Resources
Objectives
Measures
Technology People
© NEXOR 2016
o Governance
o Risk
o Controls Personnel
Physical
Procedural
Technical
o Compliance
PAS 754
Software Trustworthiness – Governance and Management – Specification
© NEXOR 2016
HOLISTIC ADVERSITY TREATMENT
[TSI/2015/047]
© Copyright 2003-2015
Adversities Risk Trustworthiness Protection
Hazards Safety Dependability
Threats Security Defence
Faults
Holistic
Stovepiped
Focus Approach Goal Treatment
∑ ƒ [Safety; Reliability; Availability;
Resilience; Security]
Source: TSI
© NEXOR 2016
o Governance
o Risk
o Controls Personnel
Physical
Procedural
Technical
o Compliance
PAS 754
Software Trustworthiness – Governance and Management – Specification
© NEXOR 2016
PAS 754 “ESSENTIAL” CONTROLS
Full Standards has approximately150 controls
Scope• Understand Requirements: Explicit/Implicit. Use Cases
• Seek Trustworthy Realisation: Minimum Feature Set
Coding
• Make Appropriate Tool Choices
• Follow Structured Design
• Follow Structured Implementation
• Seek Trustworthy Realisation
• Minimise Risk Exposure
• Practice Hygienic Coding
Tools• Tool Choices
• Production Methodology
Bugs
• Defect Management
• Dependable Deployment
• Production Methodology
Artefacts
• Source Code Protection
• Perform Trusted Software Asset Management
• Dependable Deployment
• Pre-release Review
© NEXOR 2016
o Governance
o Risk
o Controls Personnel
Physical
Procedural
Technical
o Compliance
PAS 754
Software Trustworthiness – Governance and Management – Specification
© NEXOR 2016
TRUSTWORTHINESS SCALE
Aligned to SPICE (ISO 15504)
Source: TSI
• Software trustworthiness not required
1. Nil
• Software trustworthiness delivered in a due diligence manner
2. Essential Practices
• Software trustworthiness delivered by managed processes
3. Assessed Practices
• Software trustworthiness delivered by established processes
4. Enhanced Practices
• Software trustworthiness delivered by predictable or optimising processes
5. Specialist Practices
© NEXOR 2016
AGENDA
Summary
Introduction 1
Trustworthiness 2
3
4
Building Trustworthy Software 3
Identifying Trustworthy Software 4
© NEXOR 2016
o Designed for the high end of the market Can be expensive, not always a good match
o A key feature of these schemes is they look at
your build processes…
PRODUCT EVALUATIONS
Commercial Product
Assurance
© NEXOR 2016
TICKITPLUS
A flexible, multi-level approach to IT quality and certification assessment
and can be applied at whatever level is deemed appropriate to the quality
and process maturity of the organisation and the needs of its customers.
© NEXOR 2016
o Trustworthiness
o Building Trustworthy Software
o Identifying Trustworthy Software
SUMMARY
© NEXOR 2016
MORE INFORMATION…
www.qonex.com
+44 (0) 115 952 0500
http://cybermatters.info
@QonexCyber
www.linkedin.com/company/Qonex