SVIG/python-bootcamp
7
0
Fork 1
Code Issues Pull Requests 1 Releases Wiki Activity

Update page 'OWASP test - Sloetjes'

xuanyi.wang
2023-05-25 17:24:29 +02:00
parent bb5ab8a11a
commit e04d761f0c
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
OWASP test - Sloetjes.md
+2 -2
@@ -7,8 +7,8 @@
> The Same-Origin Policy (SOP) is a critical security concept in web development. It allows a web page's scripts to interact with resources from the same origin – that is, the combination of protocol (like http:// or https://), domain, and port must match. This helps to isolate websites from each other, protecting against potential security threats like Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS). As a web developer, you must always consider the SOP when making requests to different origins, and use techniques such as CORS (Cross-Origin Resource Sharing) when you want to allow controlled access across origins. > The Same-Origin Policy (SOP) is a critical security concept in web development. It allows a web page's scripts to interact with resources from the same origin – that is, the combination of protocol (like http:// or https://), domain, and port must match. This helps to isolate websites from each other, protecting against potential security threats like Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS). As a web developer, you must always consider the SOP when making requests to different origins, and use techniques such as CORS (Cross-Origin Resource Sharing) when you want to allow controlled access across origins.
* Describe some logic to monitor failed logins, and using geolocation of the incoming IP address, the permissions of the username trying to log in, and the number of previously failed logins, a procedure to determine whether to alert administrators to a genuine break-in attempt vs a brute-force attempt. * Describe some logic to monitor failed logins, and using geolocation of the incoming IP address, the permissions of the username trying to log in, and the number of previously failed logins, a procedure to determine whether to alert administrators to a genuine break-in attempt vs a brute-force attempt.
> Monitor each login attempt, successful or not. > * Monitor each login attempt, successful or not.
> If a login attempt fails: * If a login attempt fails:
> Record the IP address, timestamp, and username. > Record the IP address, timestamp, and username.
> Increase the count of failed attempts for this IP address and/or username. > Increase the count of failed attempts for this IP address and/or username.
> If there are more than a certain number of failed attempts in a certain timeframe from the same IP or username: > If there are more than a certain number of failed attempts in a certain timeframe from the same IP or username: