3-minute product tour Urgent incident email
Assessment

Identify weaknesses in public assets
and internal systems

We assess agreed targets across web and mobile apps, infrastructure, cloud environments, and source code.
The report covers findings, business impact, and remediation priorities.

#PenetrationTesting#WebAppAssessment#InfrastructureAssessment#SourceCodeAssessment

In operationWe combine hands-on penetration testing with automated checks against published standards. Service standards

Service scope and process

Dedicated analysis nodes for each customer

Each customer’s analysis runs on dedicated nodes. Customers use separate compute resources and storage.

Every decision has a record of the supporting evidence

A single record identifies the engine behind the decision, the logs it relied on, and the action it recommended. You can submit that record as audit evidence.

Past decisions can be rerun

We record the model and policy versions used for each decision. If you question a decision from last month, you can rerun it on the same data and compare the results.

People make the final decision

AI classifies and summarizes alerts. Analysts approve response actions, including server isolation and account lockouts, before they run.

Service configuration

Assessment services

Web and mobile app vulnerability assessment

Automated scanners often miss business logic flaws that let someone view another customer's orders or change the amount charged.
An analyst reviews the application manually and documents the relevant checks against published standards.

Key capabilities

Focus on business logic flaws

We focus on issues that are difficult to detect automatically, such as privilege escalation, access to another user's data (IDOR), and payment bypasses.

Automated scanning first

Vulnerability Scanner maps pages and APIs and identifies known vulnerabilities. An analyst then carries out the manual assessment.

Findings your development team can verify

For each vulnerability, the report documents reproduction steps, screenshots, and remediation guidance so your development team can verify the finding from the report.

Post-remediation retest

Once the fixes are in place, we retest to confirm they close the gaps.

Services offered

  • Web applicationsOWASP Top 10 and Korea's assessment criteria for designated critical information and communications infrastructure
  • Mobile appsAPI traffic between Android and iOS apps and their servers
  • APIAuthentication and authorization for REST and GraphQL
  • RecheckIncludes one follow-up to verify remediation

Process

Discuss scope

Agree on targets, timing, and prohibited actions

  • Assessment plan

Automated scanning

Map the attack surface

  • Asset inventory

Manual assessment

Run the agreed test scenario

  • Vulnerability list

Reporting

Findings and remediation steps by severity

  • Findings report

Remediation verification

Retest after remediation

  • Remediation verification report

Frequently asked questions

Will testing affect services in production?

We agree on the testing window and intensity in advance. Tests that could delete data or interrupt a service require prior approval.

How is the cost determined?

The timeline depends on the number of targets and the scope of functionality. For one web service, manual assessment usually takes one to two weeks, with additional time for reporting. We provide a quote once we agree on the scope.

View all FAQs

Infrastructure and internal network penetration testing

We assess whether internet-facing exposure could put internal systems and privileged domain access at risk.

Key capabilities

Test against an agreed objective

We agree on a test objective, such as simulated theft of customer database records, then assess the paths that could lead to it.

Attack path diagram

We show how the findings link together in the path that reached the test objective.

Account and permissions review

We focus on Active Directory settings and paths to elevated privileges.

Controlled execution

Test tools and collected materials stay in the isolated Research Lab. We document their disposal when the assessment ends.

Process

Scenario design

Agree on the objective and test scenario

  • Scenario specification

External penetration testing

Test exposed assets within the agreed scope

  • Penetration test results

Internal spread

Test for lateral movement and privilege escalation

  • Attack path diagram

Reporting and improvement

We show which paths to close first

  • Findings report

Frequently asked questions

How is this different from a red team exercise?

Penetration testing aims to identify as many vulnerabilities as possible. Red team assessments also evaluate how well the security team detects and responds to activity during an authorized exercise.

View all FAQs

Cloud assessment

Seemingly minor settings can create an attack path when combined with excessive permissions.
We identify these combinations and recommend where to start.

Key capabilities

Assess multiple clouds together

We use the same checklist for AWS, Azure, GCP, and Korean cloud providers.

IAM permission path analysis

A graph shows which accounts can reach administrator privileges and how.

Containers and Kubernetes

We also review container images and cluster settings.

Proposed code changes

We provide example fixes at the code level for infrastructure as code (IaC), such as Terraform.

Process

Read-only connection

Use an assessment account with only the permissions needed

  • Permissions specification

Configuration review

Check configurations against the CIS Benchmarks

  • Assessment results

Path analysis

We map the paths from user accounts to administrator privileges

  • Attack path diagram

Reporting

Remediation priorities and example IaC fixes

  • Findings report

Frequently asked questions

Do you modify cloud settings during the assessment?

We assess cloud settings with read-only access. You make any configuration changes, and we can assist on request.

View all FAQs

Source code assessment

We analyze both your own code and the open-source libraries you use.
We document where each weakness occurs and how to address it. Where applicable, we provide an example fix for review.

Key capabilities

SAST + SCA

We check both your own code and open-source libraries for vulnerabilities.

CI/CD integration

Each pull request triggers an automated check.

Filter out false positives

AI checks whether external input can actually reach vulnerable code, helping to reduce alerts that require no action.

Suggested code fixes

We provide ready-to-paste example fixes for each programming language.

Process

Repository integration

Connect the Git repository with read-only access

  • Integration settings

Analysis

Run SAST and SCA together

  • Analysis findings

Validation

Check whether external input can reach the affected code

  • Validation results

Improvements

Code fixes for each finding

  • Assessment report
Deployment inquiries

Discuss your security needs

Tell us about your operating environment and the security scope you need, and we’ll walk you through applicable configurations.

Talk to Genox
about scope and timing.

Talk to us