In a typical SDLC cycle, software goes through quality assurance (QA) testing
includes unit, performance, system, and regression testing
Security tests should be included in QA testing
QA security testing should look for:
Plaintext passwords/weak passwords in configuration files
Default accounts on the stack (Apache, Tomcat, operating systems)
Sensitive information in log files
Input validation (XSS, SQLi)
Parameter tampering for Web applications
Insecure services used by the software team (e.g., Telnet)
Security configurations for various services (e.g., NFS)
focus not just on application but also on the stack on which the software will run
Security test case execution is carried out from two primary perspectives:
Security mechanisms are tested to ensure that their functionality is properly implemented
Security testing is conducted in relation to understanding and simulating the attacker’s approach as identified during threat modeling and other associated risk-based analyses
Three specific test type categories:
Benchmarks
used to compare estimates to actual results
Scheduled tests
include mandatory requirements to validate the security of the software and associated system(s) being tested
must be conducted regardless of whether security issues or vulnerabilities are detected or tuning is required
Exploratory tests
emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his or her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project
tester actively controls the design of the tests
tests are performed while testing to design new and better tests
successful security test execution plan assumes that:
You have done a detailed risk analysis to evaluate the software and the system(s) with which it will be associated
Test assets have been developed as part of the risk management plan and the development of a security engineering/development test strategy
Successful security test execution includes the following:
Baseline and benchmark tests have been performed to ensure that obvious security issues have been identified early in the testing cycle.
Automated test scripts have been validated as correct.
Re-benchmarking testing has been conducted after tuning.
A basis for future test comparison has been created.
The results of the security test case execution have been analyzed
Successful security test case execution completion criteria include:
The specific target security requirements and goals of the software that has been tested have been met
If a scenario outside the control of the software security group cannot be resolved, security testing may be deemed complete if the risk is accepted
situations include:
situation is outside the group’s control or contractual obligations
predetermined engagement end date is reached and company stakeholders responsible for the development of the software accept the risk of not meeting the security criteria
typically accepted if a commitment to fix the vulnerability is scheduled for the next update
software security group and stakeholders agree that the application performs acceptably, even though some security requirements or goals have not been achieved
typically have a commitment to fix the vulnerability is scheduled for the next update of the product