Merge pull request #61 from austinsonger/master
Updated README - Security
This commit is contained in:
commit
e90be158cb
15
README.md
15
README.md
@ -5243,10 +5243,20 @@ Authorization is the process of identifying what level of access the service or
|
||||
|
||||
<details>
|
||||
<summary>What is XSS?</summary><br><b>
|
||||
|
||||
Cross Site Scripting (XSS) is an type of a attack when the attacker inserts browser executable code within a HTTP response. Now the injected attack is not stored in the web application, it will only affact the users who open the maliciously crafted link or third-party web page. A successful attack allows the attacker to access any cookies, session tokens, or other sensitive information retained by the browser and used with that site
|
||||
|
||||
You can test by detecting user-defined variables and how to input them. This includes hidden or non-obvious inputs such as HTTP parameters, POST data, hidden form field values, and predefined radio or selection values. You then analyze each found vector to see if their are potential vulnerabilities, then when found you craft input data with each input vector. Then you test the crafted input and see if it works.
|
||||
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What is an SQL injection? How to manage it?</summary><br><b>
|
||||
|
||||
SQL injection is an attack consists of inserts either a partial or full SQL query through data input from the browser to the web application. When a successful SQL injection happens it will allow the attacker to read sensitive information stored on the database for the web application.
|
||||
|
||||
You can test by using a stored procedure, so the application must be sanitize the user input to get rid of the tisk of code injection. If not then the user could enter bad SQL, that will then be executed within the procedure
|
||||
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
@ -5331,6 +5341,11 @@ Authorization is the process of identifying what level of access the service or
|
||||
|
||||
<details>
|
||||
<summary>What is CSRF? How to handle CSRF?</summary><br><b>
|
||||
|
||||
Cross-Site Request Forgery (CSRF) is an attack that makes the end user to initate a unwanted action on the web application in which the user has a authenticated session, the attacker may user an email and force the end user to click on the link and that then execute malicious actions. When an CSRF attack is successful it will compromise the end user data
|
||||
|
||||
You can use OWASP ZAP to analyze a "request", and if it appears that there no protection against cross-site request forgery when the Security Level is set to 0 (the value of csrf-token is SecurityIsDisabled.) One can use data from this request to prepare a CSRF attack by using OWASP ZAP
|
||||
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
|
Loading…
Reference in New Issue
Block a user