Understand security and privacy
First describe the data, operations and people involved. Understand protections through what they prevent or allow in context. An tool name or alert list alone cannot establish that a website is safe or compromised.
63 concepts to explore with definitions and practical advice.
Search the full glossary
A reading path
1. Identity and permissions
Separate proof of identity from permission to act on an object. Check sensitive operations on the server rather than only button visibility.
- Authentication
Verification of a person’s or system’s claimed identity using appropriate factors. It may need repeating for a sensitive action. It differs from authorisation: recognising an account does not grant access to every object or operation.
- Roles and permissions
Organisation of accessible actions and resources by profile and context. Permissions require server-side checks for each request and target object. A useful test compares two accounts and a resource owned by each; hiding the access button does not protect request handling.
- Two-factor authentication
Authentication combining two distinct factor categories: knowledge, possession or biometrics. Two passwords remain a single factor type.
2. Protect exchanges
Identify transmitted data and relevant protections. Transport, content and access mechanisms address different risks.
- HTTPS
HTTP protected by TLS to encrypt exchanges and verify server identity through its certificate. This protects transport. It establishes neither editorial reliability nor absence of malicious software or correct authorisation of the site’s operations.
- CSP
Policy sent to the browser to restrict resources a document can load or execute, among other controls. It can reduce certain injection opportunities. Test it against necessary resources; it complements rather than replaces safe data handling and other application checks.
- Data minimization
Principle limiting personal data processed to what is relevant and necessary for a defined purpose.
3. Detection and recovery
Connect alerts to versions and configurations actually used. Plan recovery and verification of a restored state in an appropriate environment.
- Vulnerability
Design, code or configuration weakness that can be exploited to compromise a system.
- Incident response
Organisation of preparation, detection, response and recovery for cybersecurity incidents. Responsibilities and communications are part of the arrangements.
- Website restoration
Process of returning a website to service from copies, with checks on the pages, data and functions actually recovered.
Useful distinctions
Authentication / Roles and permissions
Authentication establishes identity in the system. Roles and permissions define allowed actions. Being signed in does not automatically grant access to every record.
Encryption / Backup
Encryption protects data readability according to its mechanism; backup supports recovery. An encrypted copy also requires an authorised way to decrypt it for restoration.
Use the vocabulary to make a decision
Situation
An editor can open a record they do not own by changing its identifier.
Before deciding
Examine authorisation applied to the requested resource. Hiding a menu link does not protect direct access.
A concrete check
Reproduce only in an authorised environment with test accounts and data.
Check permissions on the requested resource
On an authorised copy using test accounts, define who may read or change each object. Apply the rule to the request received by the server.
On a narrow screen, scroll the table horizontally to read all three columns.
| Observed signal | What to check | What it means |
|---|---|---|
| The button is hidden but the direct address responds | Test the operation with an account lacking permission. | Interface rules need a corresponding server check. |
| An editor opens another owner’s record | Compare permissions for each requested object. | A general role may not authorise this particular resource. |
| An expired session still permits a change | Check identity and permissions when the request arrives. | Sensitive operations should verify authorisation on every access. |
Next step : Keep a short matrix of account, resource, action and expected result, then verify denials as well as successes.
Technical reference : OWASP — Authorization Cheat Sheet. The scenarios and numerical examples above are educational, not measurements of this website.
Being signed in does not grant every permission
Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.
- Identity established
- Action scoped
- Resource authorised
In a demonstration application, someone has signed into their account. A separate record belongs to another account and must not be accessible to this role.
Which check decides access to that record?
A useful next step : Document expected permissions and verify them server-side with test accounts and records. This example requires no testing of real third-party accounts.
Reference to explore : OWASP · Authorization Cheat Sheet · Consulted .
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable in the main glossary.
- ACME
- ACME Renewal Information
- ACME staging environment
- AI red teaming
- Authentication
- Backup
- Brute force
- CAPTCHA
- Certificate renewal
- Cookie
- CORS
- Credential stuffing
- CSP
- CSRF
- CSV formula injection
- Cybersecurity
- Data minimization
- DDoS
- DKIM
- DMARC
- DNS-01 challenge
- DNSSEC
- Encryption
- Firewall
- GDPR
- Hashing
- HMAC
- HSTS
- HTTP-01 challenge
- HTTPS
- Incident response
- JWT
- Login
- OAuth
- OpenID Connect
- OWASP
- Partitioned cookie
- Passkey
- Phishing
- Prompt injection
- Ransomware
- Roles and permissions
- Same-origin policy
- SFTP
- Software Bill of Materials
- Spam
- SPF
- SQL injection
- SSH
- SSL/TLS
- SSL/TLS certificate
- Subresource Integrity
- Third-party cookie
- Trojan
- Two-factor authentication
- VPN
- Vulnerability
- WAF
- Website backup
- Website restoration
- XSS
- Zero trust
- Zero-day vulnerability
Frequently asked questions
Should logs retain every detail?
Keep information useful for diagnosis and follow-up within a defined framework. Passwords, tokens and unnecessary personal data should not appear in examples or test reports.
Is an automated scan sufficient?
It supplies observations within its scope. Check versions, access, sensitive journeys and recovery; interpret alerts before presenting them as confirmed incidents.
Primary reference documents
These documents explain technical concepts. Reading paths and examples are editorial methods to adapt to your project.