Software security

Question 1

sdlc

Answer 1

software development life cycle

Question 2

what is the sdlc process

Answer 2

risk assessment (requirements)
threat modelling and design review (design)
security testing and code review(testing)
static analysis (development)
static assessment and secure configuration (deployment)

Question 3

SDLC process

Answer 3

requirements
design
development
testing
deployment

Question 4

defensive programming

Answer 4

when a programmer anticipates problems and writes code to deal with them

Question 5

different forms of defensive programming

Answer 5

input validation
heed compiler warnings
architect and design for security policies
keep it simple
default dent
adhere to principle of least privelage
sanitize data sent to other systems
practice defense in depth
use effective quality assurance techniques
adopt secure coding standard

Question 6

principle of least privilege

Answer 6

every process should execute with the least set of privilages necessary to complete the job. Any elevated permission should only be accessed for the least amount of time required to complete the privileged task

Question 7

what does it mean to practise defense in depth

Answer 7

manage risk with multiple defensive strategies so that if one layer of defense turns out to be inadequate, another layer of defense can prevent a security flaw from becoming exploitable vulnerability

Question 8

what does default entry refer to

Answer 8

base access decisions on permission rather than exclusion. By default, access should be denied

Question 9

owasp

Answer 9

open web application security project

Question 10

owasp top 10 web application security risks

Answer 10

injection flaws
broken authentication
sensitive data exposure
xml external entries
broken access control
security misconfiguration 
cross-sire scripting
insecure deserialization
using components with secure vulnerabilities
insufficient logging and monitoring

Question 11

what are the consequences of non secure development?

Answer 11

??

Question 12

Threat modelling

Answer 12

structured process with these objectives:

• identify security requirements
• pinpoint security threats and potential vulnerabilities
• quantify threat and vulnerability critically and
• prioritize remediation methods

Question 13

artifacts created by threat modelling

Answer 13

abstraction of system
profiles of potential attackers - including goals and methods
a catalog of threats that could arise

Question 14

what is STRIDE

Answer 14

evaluates system detail design.
Models the in place system by building data flow diagrams
identify system entries, events and the boundaries of the system
Stride applies the general set of known threats

Question 15

general set of threats that Stride applies

Answer 15

Threat, definition, property violated
spoofing - pretending to be someone/thing other than self, authentication
tampering - modifying something, integrity
repudiation - claiming that you did not do something/were not responsible, non-repudiation
information disclosure - providing information to someone that is not authorized to access that information, confidentiality
denial of service - exhausting resources needed to provide service, availability
elevation of privilege - allowing someone to do something that they are not authorized to do, authorization

Question 16

CVSS

Answer 16

Common vulnerability scoring system

captures the principle vulnerability and produces a numerical severity score

Question 17

SAST vs DAST

Answer 17

sast – static security tests
dast - dynamic security tests

SAST and DAST are application security testing methodologies used to find security vulnerabilities that can make an application susceptible to attack.

Static application security testing (SAST) is a white box method of testing. It examines the code to find software flaws and weaknesses such as SQL injection and others listed in the OWASP Top 10.

Dynamic application security testing (DAST) is a black box testing method that examines an application as it’s running to find vulnerabilities that an attacker could exploit.