Please enable JavaScript.
Coggle requires JavaScript to display documents.
Security - Coggle Diagram
Security
Technical Threats
-
-
-
-
-
-
-
-
-
-
-
-
-
Path traversal
Exploits insufficient security validation or sanitization of user-supplied file names, such that characters representing traverse to parent directory are passed through to the operating system's file system API.
-
-
-
-
-
-
-
-
-
Testing
Root Cause Analysis
It is the process of discovering the root causes of problems in order to identify appropriate solutions.
-
Define the problem
what is the problem, what happens if it don't get addressed, what are the benefits to solving it
-
-
Prioritise the causes
prioritise the causes from the previous step, try to reduce the list, confirm the methodology that's going to be used
-
Implement the change
who will implement the change, when will the change be implemented by, what does success look like
Monitor and sustain
how will the solution be monitored, how will the new solution work/ be embedded into existing business processes, how will the impact of the solution be analysed
Fishbone Diagrams
A fishbone diagram is a visual root cause analysis tool to identify the possible causes of the identified problem(s)
-
A fishbone diagram may also be referred to as a cause and affect diagram , an Ishikawa or a Herringbone diagram
-
-
-
Step 4 - Identify all the possible causes of the problem(s) by asking why. Add ideas as a branch from the categories
Step 5 - Continue to ask why about each cause and write sub causes branching off the causes identified
-
Testing Methods
Concept testing
The process of using surveys to evaluate consumer acceptance of a new product idea prior to the introduction of a product to the market.
-
Stress testing
It is a software testing activity that determines the robustness of software by testing beyond limits of normal operations
Penetration testing
A method of gaining assurance in the security of an IT system by attempting to breach some of or all of that system's security using the same tools and techniques as an adversary might.
Black box testing
A method of software testing that examines the functionality of applications without peering into its internal structures or workings
White box testing
A form of application testing that provides the tester with complete knowledge of the application being tested including access to source code and design documents