The security model of web applications

Practice

shows how we can maintain continuous web application security from a black-box testing perspective.

Comments

To leave a comment

If you have any suggestion, idea, thanks or comment, feel free to write. We really value feedback and are glad to hear your opinion.

To reply

Comment

To confirm that you are not a bot, answer:

Name

Email(not published)

Vote

Lectures and tutorial on "information security - Cryptography and Cryptanalysis. Steganography. Information protection"

Terms: information security - Cryptography and Cryptanalysis. Steganography. Information protection

Digital fingerprint of the device

Online tests with answers and diagrams on software security

Authentication and authorization in information technology

Security testing: SAST, WAF, DAST, IAST, and RASP

Bogon filtering of IP addresses

Types of web API, SPA, and JWT vulnerabilities in 2022

Cache poisoning

Cross-site request forgery (CSRF)

XSS (cross-site scripting) — its essence and methods of protection

Cross-site tracing (XST)

Cross-server attack (XSA)

CURL — a tool that can be used to force parameters into a web request

Direct Static Code Injection

File inclusion

Full path disclosure (FPD)

HTTP request smuggling

HTTP response splitting

LDAP injection

Local file inclusion

Pharming — what is pharming? Preventing pharming

Phishing — an attempt to obtain confidential information

The poison null byte

Directory traversal attack

File inclusion

Server-side includes (SSI)

Session fixation

Session hijacking

SQL injection: methods of protection, static analysis

The security model of web applications

Honeypot — a lure for intruders

Integrity control of data or resources of a computer system

Message authentication (Message Authentication Code, MAC)

Creating a self-signed trusted certificate for development — a ready-made script

Symmetric cryptosystems

Universally unique identifier (UUID)