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:25:29 +02:00
parent e04d761f0c
commit 483a5cad87
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
OWASP test - Sloetjes.md
+8 -8
@@ -8,14 +8,14 @@
* 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:
> Use a geolocation service to identify the location of the IP. > * Use a geolocation service to identify the location of the IP.
> Compare this location to the known or expected location of the user. > * Compare this location to the known or expected location of the user.
> Check the user's permission level. Higher-risk users (like admins) may warrant tighter security measures. > * Check the user's permission level. Higher-risk users (like admins) may warrant tighter security measures.
> If the location doesn't match or there are too many attempts, it may be a brute force or break-in attempt. Notify the administrators based on these factors. > * If the location doesn't match or there are too many attempts, it may be a brute force or break-in attempt. Notify the administrators based on these factors.
* Describe the lifetime of a session-only cookie, and how this could be used to create a session authorization token. * Describe the lifetime of a session-only cookie, and how this could be used to create a session authorization token.
> Session-only cookies, also known as transient cookies, exist only in the temporary memory of the browser and are deleted when the user closes their browser. This means the lifespan of a session-only cookie is tied directly to the duration of the browsing session. These cookies can be used to create a session authorization token, which represents the user's session. This token can be used to maintain the state of the session and to track the user's activities during the session, making it easier to manage user authorization and access controls. > Session-only cookies, also known as transient cookies, exist only in the temporary memory of the browser and are deleted when the user closes their browser. This means the lifespan of a session-only cookie is tied directly to the duration of the browsing session. These cookies can be used to create a session authorization token, which represents the user's session. This token can be used to maintain the state of the session and to track the user's activities during the session, making it easier to manage user authorization and access controls.