Sparlio
01HOME
02About
03SERVICES
04Contact
Language

Website & Web Application Security Assessment

We review the security of your website or web application within an agreed scope and report the risks we find with evidence, likely impact and recommended fixes.

  • Written authorisation and agreed scope only
  • Verified findings with evidence
  • A prioritised action plan

What does Sparlio do in a security assessment?

Sparlio reviews the security of your website or web application with your written authorisation and within a scope agreed in advance, and reports verified risks with evidence, likely impact and recommended fixes. The assessment goes beyond listing a scanner’s output: we learn how the system is built and used, check whether each finding is real, and prioritise actions your technical team can apply. Which systems are reviewed, which methods are used and when testing takes place are agreed in writing before work begins.

WHY

Why have a security assessment?

Websites grow over time with new features, plugins, user accounts and integrations. These changes can introduce new risks or slowly weaken a configuration that was once secure. A regular assessment helps you catch problems before they grow, see what to fix first and give your technical team a clear improvement plan.

  • 31%

    In the 2026 Verizon DBIR, 31% of breaches began with the exploitation of a vulnerability, overtaking stolen credentials for the first time in the report’s 19 years.

  • 11,334

    New vulnerabilities reported in the WordPress ecosystem in 2025; 91% were in plugins and 46% had no fix when they were made public.

SCOPE

What can the assessment cover?

The scope of each project depends on how the system is built and on the test plan agreed with you. Depending on your needs, the following areas can be assessed.

01Internet-facing assets

  • The agreed domains and subdomains
  • Pages and services reachable from the internet
  • Visibility of admin panels and access points
  • Files, directories or test environments left exposed by mistake

02Server and site configuration

  • SSL/TLS configuration
  • Essential web security headers
  • Whether error and debug messages leak information
  • Known risks of the platform and components in use
  • Observable security issues in CMS, plugin and software versions

03Login and user permissions

With the test accounts you provide and within the permitted scope

  • Basic behaviour of login and session management
  • Access boundaries of user roles
  • Situations that could lead to unauthorised access
  • How account and password flows affect security

04Forms, file uploads and APIs

When included in scope

  • How forms and user input are handled
  • Basic controls on file upload fields
  • Access and response behaviour of the agreed API endpoints
  • Error responses that share more than they should

Not every project covers all of these items. The components to be tested and the methods to be used are agreed in writing before work begins.

PROCESS

How does the work proceed?

01

Initial call and scoping

We discuss the website or application to be reviewed, what the system is used for and what you expect from the assessment. Domains, subdomains, test environments, user accounts and out-of-scope systems are defined.

02

Authorisation and test plan

Before work begins, the system owner’s written authorisation is obtained and the test methods, time window and limits on the system are set. Third-party services and systems owned by other organisations are not included unless separately authorised.

03

Security assessment

The agreed systems are reviewed within the approved scope and time window. If an unexpected service impact or stability risk is noticed, the check in question is stopped and you are informed.

04

Verifying findings

Results are reviewed for evidence, likely impact and severity. Results without sufficient evidence, or that may be false positives, do not enter the report as verified findings.

05

Report and action plan

Findings are explained so technical teams can follow them, each with a recommended fix and a priority. The report is written so managers can see the overall picture and technical teams can apply the fixes.

06

Retest after remediation

Once your fixes are complete, you can ask for the related findings to be checked again. The scope and timing of this retest are set at the proposal stage.

REPORT

What report do you receive at the end?

The report follows the agreed scope and includes:

  • An executive summary and overall assessment
  • The domains, applications and components tested
  • Assets left out of scope
  • A description of each finding
  • The severity and priority of each finding
  • Evidence and likely impact
  • Recommended remediation steps
  • A prioritised action plan
  • Retest results, if a retest was done
HOW WE WORK

Authorisation, scope and data security

Sparlio carries out security assessments only on systems you own or have authorised in writing to be tested. Articles 243 and 244 of the Turkish Penal Code make it a crime to enter an information system unlawfully or to block or disrupt it, so work never starts without the system owner’s written consent and a signed scope document.

Tests that could cause downtime, load tests and actions that could change the system are not performed unless separately agreed in writing. Third-party services and infrastructure stay out of scope unless the relevant authorisation is obtained.

Access details should be shared only as far as needed and through a secure method; do not send passwords, API keys or similar secrets through the website request form. Personal data is accessed only as far as needed to verify a finding and is never copied. Subject to any legal obligations, findings and reports are shared only with the people you authorise.

EDGE

Which principles do we work by?

  1. 01We report verified findings, not raw tool output; results without solid evidence stay out of the report
  2. 02We work only with written authorisation, within the agreed scope and time window
  3. 03We never run tests that risk downtime unless they are agreed in writing
  4. 04As a team that builds websites, we write fixes as steps your team can actually apply
CURRENT · LAST REVIEWED: NOVEMBER 2026

What changed in web security over the past year?

  • October 2026

    Let’s Encrypt moves to 64-day certificates by default

    Let’s Encrypt announced that from 10 February 2027 its certificates will default to 64-day lifetimes, with 45 days planned for 2028. Renewal set-ups tied to a fixed number of days need a review.

  • September 2026

    Chrome now asks before HTTP connections by default

    Chrome 154, released on 22 September 2026, prompts users by default before connecting to a site over insecure HTTP. Pages that cannot be served over HTTPS may now greet visitors with this warning.

  • June 2026

    USOM notices moved to the Cyber Security Presidency

    USOM’s security notices, CVE and incident-reporting processes and malicious-link lists now continue at siberguvenlik.gov.tr; the .txt feed of the malicious-link lists ended on 1 June 2026. Systems that pull these lists automatically need to switch to the API services.

    Source: USOM
All changes (6)
  • March 2026

    Maximum TLS certificate lifetime cut to 200 days

    Under a CA/Browser Forum ballot, public TLS certificates issued from 15 March 2026 may be valid for at most 200 days; the cap falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Automated, monitored renewal now matters even more.

  • January 2026

    KVKK limits breach notices on its website to 60 days

    Under Board decision 2025/2451 of 25 December 2025, data breach notices now stay on the KVKK website for at most 60 days; there was no limit before. The duty to notify the Board of a breach still applies.

    Source: KVKK
  • 2025

    OWASP Top 10:2025 released

    The most widely used list of web application risks was updated for the first time since 2021: Software Supply Chain Failures and Mishandling of Exceptional Conditions are new categories, and Broken Access Control stays at number one.

    Source: OWASP
REMEDIATION

Who fixes the findings?

Your own technical team can apply the report. If you prefer, Sparlio’s web development team can take on the fixes; the scope of the retest is then planned separately.

See our web development service
FAQ

Security assessment FAQ

A security assessment is a review of the security risks in a website or web application within a scope agreed in advance. Sparlio reports the findings whose evidence has been checked, together with their likely impact and recommended fixes.

Websites and web applications that the system owner has authorised in writing can be assessed. Domains, subdomains, test environments, user accounts and any APIs are defined in the scope before work begins.

Not every assessment needs an admin account. Reviewing internet-facing areas usually starts without credentials. If user roles or features behind login are in scope, test accounts limited to that scope may be requested.

Work on a live environment is carried out only with the system owner’s explicit written authorisation and an agreed test plan. Where possible, a test or staging environment is recommended first. The scope and timing of any checks on the live environment are set in advance.

System stability is protected throughout the assessment. Actions that risk downtime or heavy load are not performed unless separately agreed in writing. If an unexpected risk is noticed, the check is stopped and the client is informed.

It depends on the number of domains and applications, the size of the application, the areas behind login and the information provided. The duration and schedule are shared once the scope is clear.

The fee depends on the number of domains and applications, the areas behind login, the APIs and whether a retest is needed. It is given in writing in the proposal once the scope is clear.

The report covers the scope reviewed, the severity of each finding, the evidence, the likely impact and the recommended fixes. Findings are explained so technical teams can act on them and are listed in order of priority.

No. The assessment shows what was observed within the agreed scope and working time. No single review can guarantee that every possible risk will be found or that a system is completely secure.

No. On its own, this service does not provide an official certification or a regulatory compliance document. If work is needed for a specific standard or regulation, its requirements must be defined separately and the scope set accordingly.

No. Sparlio’s security assessment does not replace work that requires a TSE-approved penetration testing firm (for example the e-commerce trust seal) or the mandatory penetration tests required by BDDK, SPK and Central Bank (TCMB) regulations. If you have such an obligation, you need to work with a firm that holds the required certification.

No. Turkey’s Cyber Security Law No. 7545 requires public bodies and critical infrastructure to obtain cyber security services from experts and companies authorised and certified by the Cyber Security Presidency. Sparlio is not an authorised company in this sense, so this service is not offered to public bodies or critical infrastructure operators.

Yes. Once the fixes are complete, you can request a retest to check whether the related findings have been resolved. Its scope and timing are set at the proposal stage.

At first, the website address, an authorised contact at your organisation and your expectations are enough. If test accounts or other access details are needed, a secure sharing method is agreed once the scope and authorisation are clear.

SERVICE AREA

Based in Istanbul, we deliver across every district from Beylikdüzü, Silivri, Avcılar, Bakırköy and Esenyurt to Kartal, Pendik, Maltepe, Üsküdar and Kadıköy, and nationwide.

OTHER SERVICES

We also do these.

04
Web Development
Corporate sites, e-commerce, landing pages on Next.js & Shopify.
Details
08
GEO Optimization
Transparent GEO work for accurate brand visibility in ChatGPT, Gemini and Google AI Mode.
Details
01
Performance Marketing
ROAS-driven performance agency across Google, Meta, TikTok, X and Pinterest.
Details

Let’s define the scope together.

Send us your assessment request for your website or application; we will set the scope and work plan together.

Do not send passwords, API keys or similar secrets through the request form; if needed, a secure sharing method is agreed once the scope is clear.

Last updated: 5 November 2026