Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Web resources

    Security, privacy and compliance

    Authorities, guidance and security tools help prioritise risks and verify safeguards. A general alert does not prove a particular site is vulnerable; its version and configuration matter.

    Inventory software, versions and sensitive journeys. For each relevant advisory, check whether the installed version and configuration are affected, then assign the fix and its verification.

    AI-generated illustration

    Editorial method

    A directory made to be useful, not merely long.

    Selection prioritises recognition within the field, professional use and reference status. Highly specialised documentation entries are consolidated under their main resource.

    01

    Official foundations

    Standards bodies, official documentation and public authorities are used as primary reference points.

    02

    Professional tools

    Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.

    03

    Independent reading

    Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.

    Before choosing

    Compare on three practical questions

    Security, privacy and compliance
    CriterionQuestion to resolve
    ScopeDoes the resource concern your software version and actual exposure?
    AssessmentIs an automated score sufficient, or must access, data and logs be examined?
    RecoveryIs there an owner, a tested backup and an incident procedure?

    Keep a short decision record: requirement, source, observed result and unresolved point. Test the same task with each candidate instead of comparing marketing lists of features.

    Search and filter

    Official starting points for this topic

    Compare their role and documentation before selecting a tool. Inclusion is not a ranking.

    11 resources displayed

    The date applies to the linked document, not to a review of every service feature.

    Security, privacy and compliance

    CERT-FR

    French alerts, advisories and bulletins on vulnerabilities and incidents.

    CERT-FR · ANSSI · Source consulted

    Use it for : Cross-check a security notice against versions actually deployed.

    Documented characteristics
    Resources
    Alerts, security advisories and threat reports
    Source
    CERT-FR · ANSSI
    Scope
    Published information; no diagnosis of your installation

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: an advisory mentions a vulnerability in a component used by the site. The product name alone does not establish that your version and configuration are affected.
    Useful check
    Distinguish an alert about immediate danger, an advisory describing a vulnerability and remedies, and a threat report. Compare affected versions, prerequisites and vendor measures with your actual inventory.
    Interpretation and next step
    Record the document reference and revision date. An advisory is not proof of compromise: take the appropriate action, then verify the version and operation after remediation.

    Official documentation ·

    FranceInstitution / standard
    cert.cyber.gouv.frVisit official website
    Security, privacy and compliance

    OWASP

    Open references and projects for Web application security. Choose the appropriate project: testing methodology, prevention guidance or risk list. Retain version and test scenario; a risk list is not an audit of your application.

    OWASP · Source consulted

    Use it for : Use security resources as a testing basis, not proof of compliance.

    Documented characteristics
    Catalogues
    OWASP Top 10
    Specification
    ASVS
    Documentation
    WSTG

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: a team wants to check that a customer cannot view another customer’s order. Citing only the Top 10 describes neither the requirement nor the test performed.
    Useful check
    Use the Top 10 to frame the risk, ASVS to define requirements and WSTG to prepare tests. Record each document version and adapt the scenario to your test accounts and data.
    Interpretation and next step
    Retain the expected result, observed result and evidence of the fix. Reading a reference or passing a single test does not certify the security of the entire site.

    Official documentation ·

    Official documentation · OWASP ASVS

    Official documentation · OWASP WSTG

    InternationalCommunity / learning
    owasp.orgVisit official website
    Security, privacy and compliance

    Have I Been Pwned

    Check whether addresses and domains appear in known data breaches.

    Have I Been Pwned · Source consulted

    Use it for : Use the service within internal breach-response procedures.

    Documented characteristics
    API
    Pwned Passwords · k-anonymity
    Prefix
    SHA-1 → 5
    Endpoint
    GET https://api.pwnedpasswords.com/range/{prefix}
    Headers
    Add-Padding: true
    Syntax
    SUFFIX:COUNT

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    To understand Pwned Passwords, use a public demonstration string, never a real password. Compute its SHA-1 hash locally and send only the first 5 hexadecimal characters to the service. Then compare the remaining 35 characters with the returned suffixes, without sending the string or its full hash.
    Useful check
    The Add-Padding: true header adds padding rows; ignore rows whose count is zero. Compare the exact suffix. An HTTP 200 status confirms a response to the prefix lookup; it does not mean that the password being checked was found.
    Interpretation and next step
    Wait until input is complete instead of querying on every keystroke. No match does not guarantee password security. Using SHA-1 in this protocol is not a recommendation for password storage; looking up breaches by email address is a separate service.

    Official documentation ·

    Official documentation · Have I Been Pwned — Pwned Passwords API

    InternationalService / platform
    haveibeenpwned.comVisit official website
    Security, privacy and compliance

    NIST Cybersecurity Framework

    Cybersecurity risk-management framework for organisations. Use profiles to compare current and target states for the organisation’s activities. Tie outcomes to responsibilities and evidence without presenting the framework as a certification.

    NIST Cybersecurity Framework · Source consulted

    Use it for : Map framework functions to the organisation’s responsibilities.

    InternationalInstitution / standard
    nist.govVisit official website
    Security, privacy and compliance

    VirusTotal

    Analysis of files, URLs, domains and security indicators.

    VirusTotal · Source consulted

    Use it for : Interpret results cautiously and protect confidentiality of submitted files.

    Documented characteristics
    Quota
    Public API → 4 / min · 500 / day
    Commercial use
    Public API: commercial products and services prohibited
    Business workflows
    Public API: business workflows without new files prohibited

    Verification path

    1. Identify file and report
    2. Interpret each analysis state
    3. Check the offering conditions

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: review a file analysis report. Match the exact file hash, date and per-engine results. An identical filename does not establish that the analysed bytes are the ones you are examining.
    Useful check
    No detection is not proof of harmlessness. undetected means the engine has no opinion; failure or a timeout is not a favourable result. Review states and context rather than a single counter.
    Interpretation and next step
    Public API quotas and use restrictions are separate. Contributing new files does not remove the ban on commercial products or services. Check the permitted offering before any integration; this example runs no analysis.

    Official documentation ·

    Official documentation · VirusTotal · Analysis states

    InternationalTool / software
    virustotal.comVisit official website
    Security, privacy and compliance

    SSL Labs

    Qualys SSL Server Test examines TLS configuration on an Internet-accessible server. The report concerns that connection, not the entire application or its access controls.

    Qualys SSL Labs — SSL Server Test · Source consulted

    Use it for : Check the actual hostname and read certificate and protocol details. After changes, repeat the test and visitor journey; a good TLS grade does not check account authentication or form processing.

    Documented characteristics
    Scope
    TLS configuration of a public web server
    Checks
    Certificate, protocols and cipher suites
    Measure
    TLS grade; does not measure all application security

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: a site earns a good TLS grade, but an account can still access someone else’s data. The grade does not assess that application permission.
    Useful check
    On a server you are authorised to test, record the hostname, date, certificate and supported protocols. If several endpoints appear, examine their results separately.
    Interpretation and next step
    After fixing TLS configuration, retest the affected endpoint. Keep separate checks for accounts, permissions and business workflows; a TLS grade validates none of these.

    Official documentation ·

    InternationalTool / software
    ssllabs.comVisit official website
    Choose a starting point

    What each category helps you decide.

    These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.

    Security, privacy and compliance

    Authorities, guidance and security tools help prioritise risks and verify safeguards. A general alert does not prove a particular site is vulnerable; its version and configuration matter.

    Questions to check
    • Separate preventive guidance from an active vulnerability notice.
    • Assign who applies, tests and documents a correction.
    • Check who receives alerts, what data is exposed and how access is revoked.

    A practical use : Inventory software, versions and sensitive journeys. For each relevant advisory, check whether the installed version and configuration are affected, then assign the fix and its verification.

    What this cannot prove : A scanner or alert list proves neither safety nor compromise. Personal-data questions require an assessment tailored to the incident.

    Examples : ANSSI · OWASP

    Related guide : Test website restoration before an incident

    Explore troubleshooting situations

    Troubleshooting methods

    A security signal needs context and assessment by its responsible owner. These situations describe careful checks and evidence to preserve. They do not diagnose compromise and never require sharing a secret to obtain help.

    A message demands urgent account action

    What you observe
    A message announces a domain or service problem and asks you to open a link, pay or provide login information.
    Before drawing a conclusion
    Urgency and the displayed sender name do not establish a message’s origin. Verification should use a path independent of the received link.
    Verification step
    Visit the service through its usual address or contact its owner through an already known channel. Preserve the message for authorised analysis, without opening attachments or copying a password into a support request.

    A troubleshooting log contains excessive data

    What you observe
    An excerpt intended to explain an error exposes a request’s contents, identifying information or sensitive values.
    Before drawing a conclusion
    Visibility into a problem does not justify collecting or sharing every available value. Logging should serve a known purpose.
    Verification step
    Prepare a minimal excerpt with technical context, time and outcome. Have retained fields, recipients and log access reviewed. Use demonstration data to reproduce the error when sufficient.

    A report shows no alert for a sensitive task

    What you observe
    A tool finishes without a displayed finding, but its scope does not clearly identify the functions and versions examined.
    Before drawing a conclusion
    No findings can mean no defect was detected within that check. It does not prove every site task is free of risk.
    Verification step
    Preserve the check’s scope, version and exclusions. Ask the security owner to assess unexamined areas. Do not run intrusive tests against a third-party or public service without explicit authorisation.
    Another case to examineThe account is closed, but an integration retains access
    Situation
    Someone leaves the project and their main account is disabled. A connected application or service access may still rely on a separate authorisation.
    Before drawing a conclusion
    Removing a user in one tool does not demonstrate revocation of every delegation associated with the project.
    Practical check
    Review accounts, authorised applications and service access with the owner. Remove unnecessary permissions and use an authorised test account to check that the team’s intended operations still work.

    Reference : OWASP · Authorization

    Further documentation

    Keep useful data when changing tools

    Before making a resource part of website operations, plan for updates and an exit too. These checks concern your trial results without assuming features or prices of a particular plan.

    Keep advisory references

    Record product, version, configuration and primary advisory. An alert without affected versions cannot establish whether the site is affected.

    Export without exposure

    Limit reports to information needed for diagnosis. Tokens, passwords and unnecessary personal data should not travel with exports.

    Remove an integration

    Inventory service accounts, tasks and permissions used. Removing a tool should include access no longer needed under the team’s procedure.

    Transparency

    Editorial scope and third-party websites

    This non-exhaustive directory had its data consistency and links checked on 2 October 2026. Some websites restrict automated checks. It contains external links to independent websites. Their availability, content, prices, cookies and terms may change. Française du Numérique does not control them and receives no commission for their inclusion.

    Directory questions

    Selection, independence and updates.

    Entries describe resources from their publishers’ pages and provide a source, category, purpose and checking date. The selection covers different Web tasks rather than ranking every available provider. Open the cited source to check current scope, availability and conditions before relying on a service.

    No. Inclusion identifies a resource to examine; it does not certify every feature, price, policy or result. Compare the resource with your actual task, country, language and technical requirements. Confirm current conditions with its publisher before committing time, data or money.

    Yes. Search the displayed catalogue, combine the available filters and clear them to return to the full list. Every entered word must match the indexed text. The visible result count describes this selection, not the entire Web. Individual category pages and direct links remain available without JavaScript.

    Describe the service, time, action and error message. Remove secrets, tokens, personal data and unnecessary files. Use the official support channel and request an appropriate secure method if sensitive material becomes indispensable to the investigation.

    Check the product, version, exposure conditions and primary advisory. Have the technical owner assess these before changing the service. Document the decision and unresolved points; do not present a matching name alone as evidence of a vulnerability.

    Compare using observable evidence

    Before choosing a resource, run a limited trial using the same data and task. Keep the outcome and its limitations rather than a ranking based on familiarity.

    Assess controls in an authorised environment using test data. Check access removal, recovery and log visibility. Connect each observation to an owner and correction; a favourable scan does not guarantee absence of vulnerabilities.

    Use precise terms

    Two distinctions before comparing resources

    Successful sign-in and browser input checks do not establish every server-side control.

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    HTTP · 503
    503 · Retry-AfterTemporary unavailability; a delay may be indicated without guaranteeing recovery.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.