Payment processor

Paynet: web and mobile penetration testing, mapped requirement by requirement to the NBM

Paynet wanted to assess the security posture of its externally exposed systems and applications, web and mobile, against both industry best practice and the requirements of the National Bank of Moldova.

Engagement
Penetration testing and information-security assessment
Reference
NBM requirements; beyond the OWASP Top 10

At a glance

The challenge

Assessing the cybersecurity posture of publicly exposed systems and applications (web and mobile), in accordance with the requirements of the National Bank of Moldova.

The approach

Structured, controlled penetration testing using recognized methodologies extending beyond OWASP Top 10, with a strong focus on regulatory compliance and requirement-by-requirement reporting.

The outcome

Comprehensive, well-structured deliverables aligned with both technical and regulatory expectations — audit-ready and supporting internal governance processes.

In the client’s words

"The testing activities were executed in a structured and controlled manner, leveraging recognized methodologies and extending beyond standard frameworks such as the OWASP Top 10. In particular, the engagement demonstrated a strong focus on NBM regulatory compliance, with results clearly mapped against specific requirements. The reporting approach was granular and systematic, providing requirement-by-requirement validation, which significantly enhanced traceability, auditability, and ease of follow-up actions."

— Executive Director, Paynet Services SRLQuoted from the original letter, written in English.

How we run an engagement like this

The steps below describe our usual method for this type of engagement, not the details of the client’s project.

  1. Applicable requirements

    We start from the National Bank of Moldova requirements that apply to the system and turn them into a checklist.

  2. Technical testing

    We test the exposed systems and applications (web and mobile) as a real attacker would, beyond the OWASP Top 10.

  3. Documentation and evidence

    We review the client’s policies, procedures and evidence on their merits, not just their form.

  4. Requirement-by-requirement assessment

    Every requirement gets a verdict and the evidence behind it, so an auditor can follow the reasoning.

  5. The report

    A report ready for management, internal governance and the regulatory submission.

  6. Remediation review

    After the fixes, we check the open points again and confirm what has been closed.

What the client received

As the client describes them in the letter.

  • Requirement-by-requirement reporting: traceability, auditability, easy follow-up
  • Comprehensive, well-structured deliverables aligned with technical and regulatory expectations
  • Support for internal governance and potential supervisory reviews
  • High-quality communication and engagement throughout the project

Related services

Other case studies

← All case studies

Want the same results for your organization?

Book a free consultation and get a quote tailored to your scope — with no hidden costs.