Security Testing

Penetration Testing and Security Review

GG Tech Teknoloji performs authorized security testing of web applications, APIs, networks and infrastructure, and source code. Every test is carried out with the written permission of the system owner, within a scope and dates agreed in advance; findings are delivered only to the system owner. This page puts the scope of the service, the team, the method and the rules we follow on the record.

Last updated:

What we test

Our security testing service has four parts. Our scope is limited to these; which of them apply to an engagement is agreed in writing with the system owner before testing starts.

Web application penetration testing

Testing authentication, session management, authorization, input validation and business-logic flaws against the running application.

API testing

Checks on the API endpoints behind applications: authentication, object-level and function-level authorization, data exposure and input validation.

Network and infrastructure testing

Identifying exposed services, misconfigurations and outdated software on the servers and network components in scope.

Source code review

Reading application code for security: authorization checks, input handling, secret management and dependencies.

Team

Tests are carried out by GG Tech's security testing team. The team has two roles.

Test lead

Agrees the scope and dates with the system owner, obtains written permission, manages the test and reviews the report before delivery.

Testers

Carry out the test within the agreed scope, verify the findings and document them.

At company level, GG Tech Teknoloji holds an ISO/IEC 27001:2022 Information Security Management System certificate (Certificate No YS-451-01). The certificate and its verification details are published on the Due Diligence page.

Method

For web application and API tests we follow the OWASP Web Security Testing Guide (WSTG). A test has four stages.

1. Scoping

The systems, addresses, test accounts, date range and contact people are agreed in writing.

2. Testing

Testing is done within the agreed scope and on the agreed dates. Systems outside the scope are not touched.

3. Reporting

Findings are delivered to the system owner in a report, with a severity rating and a remediation recommendation.

4. Retest

After fixes are made, the related findings are tested again and the result is recorded in the report.

Rules of authorization

The rules below apply to every test, without exception.

  • Every test is carried out with the written permission of the system owner. No system is tested without written permission.
  • Testing is limited to the systems and the date range written in the permission.
  • We do not run denial-of-service tests or destructive tests that delete or corrupt data.
  • Once a vulnerability has been demonstrated, we do not access more data than necessary; data we come across is not copied or shared.
  • If something that could affect the system is noticed during a test, testing stops and the system owner is told immediately.

Reporting and confidentiality

Findings are delivered only to the system owner; they are not shared with third parties or published. The report contains the following.

  • The scope tested and the test dates.
  • A description of each finding and the component it affects.
  • A severity rating for each finding.
  • A remediation recommendation for each finding.
  • The final status of the findings, when a retest was done.

Who we work for

So far we have carried out security tests in the following areas. For confidentiality we do not publish client names.

Projects we build

Security testing of the software GG Tech develops.

Municipalities

Web applications and systems owned by municipalities.

Public institutions

Applications and systems owned by public institutions.

Education platforms

Online education and academy platforms.

Vulnerability disclosure

If you have found a security vulnerability in ggtech.co or in a system operated by GG Tech, write to the address below. It is enough to tell us the affected address, how to reproduce the issue and its possible impact.

When reporting, we ask you to go no further than needed to show the issue, not to access other people's data, not to disrupt the service, and not to publish details until the issue is fixed. Machine-readable contact details are at ggtech.co/.well-known/security.txt.

Contact

For a security testing request or a vulnerability report, you can reach the security testing team at:

info@ggtech.co

Due Diligence pagesecurity.txt

Book a callWhatsApp