ODSA - Data Transfer Security Associate
- Issuer
- OPSWAT
- Holder
- Cristian Istrate (person on our team)
- Valid until
- 19 Sept 2027
- Credential no.
- tJN83ulfSg
We use public standards that anyone can look up. Each finding we report has an ID from our check catalogue, an OWASP test reference, a MITRE ATT&CK technique, a CWE weakness class, a NIST CSF 2.0 function and a CVSS v3.1 vector you can recalculate yourself.
For each standard we explain what we use it for and where it shows up in our work. We also say plainly where we can certify you and where we can't.
The standard methodology for testing web applications. It sets the order of work on a web pentest, so what gets covered follows a checklist and doesn't depend on which engineer does the job.
The same for mobile apps: how data is stored, how the app talks to the operating system, cryptography and the code-quality checks a mobile build needs.
The phases of a penetration test from start to finish: agreeing the scope, gathering information, threat modelling, exploitation and reporting.
Every finding we report is tagged with an ATT&CK technique. The field is mandatory, so you can compare what we found with what your detection already covers.
The type of weakness behind the finding. It helps your developers spot the same mistake in other parts of the code.
There is no NIST CSF certificate, so nobody can be certified against it. We assess your organisation against the six functions of CSF 2.0 and show you, one function at a time, where you already meet it and where you don't. Govern is at the centre of CSF 2.0. It covers policy, oversight and supplier risk, which is what most security questionnaires ask about.
Organisational context, risk strategy, roles and responsibilities, policy, oversight and supplier risk.
Asset inventory, risk assessment, and vulnerability identification.
Access control, awareness training, data security, and maintenance.
Monitoring and analysing security events.
Incident handling, communication, analysis, and mitigation.
Restoration, continuity planning, and post-incident communication.
Anyone can recalculate the score from its vector, so you can check how we arrived at each severity. Other vendors and tools read it the same way.
We are not an accredited certification body and we don't issue the ISO 27001 certificate. We check your organisation against each of the 93 Annex A controls and give you written evidence of where you stand. You go into the formal audit knowing what is still open.
Security policies, suppliers, buying cloud services, threat intelligence and incident management.
Background checks, employment terms, security training, the disciplinary process, NDAs and remote working.
Physical perimeters, secure offices, where equipment sits, clear desk and clear screen, and safe disposal of storage media.
Access rights, privileged access, authentication, cryptography, vulnerability management, secure coding, logging and monitoring.
Section 05 maps the findings to compliance frameworks and Section 06 lists every check we ran. You can send the PDF as it is to a large customer, your DPO or an ISO or NIS2 auditor.
In Section 03, each finding lists its check ID from our catalogue (for example VA-WEB-HEADERS-001), the CVSS v3.1 score and vector, the OWASP Top 10 category, the MITRE ATT&CK technique and the CWE root cause.
Section 05 counts the open findings by OWASP Top 10 category (for example A05:2021 Security Misconfiguration), MITRE ATT&CK tactic, CWE class and NIST CSF 2.0 function (PR.DS, PR.IP, PR.AC, DE.CM). Management can see quickly where the same kind of problem keeps coming back.
Auditors also want to know what was tested and passed. Section 06 lists all 105 checks in 14 categories, how each was run (automated, semi-automated or manual) and its result.
Each certification shows who issued it, who holds it (the company or a named person) and a link where you can check it.
Only certifications issued to the company as a legal entity are listed here. If there are none, we say so.
A personal certification belongs to the person who passed the exam. We always show their name, the credential number and a link to check it with the issuer.
Certifications we are still working towards sit in a separate 'In progress' group without a check mark, so nobody mistakes them for ones we already hold.
The company holds no certifications of its own.
These are personal certifications. They belong to the person named, not to the company.
Not obtained yet. We list them so you know what's coming.
Start with a single scan. Add testing and monitoring when you need them, or put several services together for 1 or 3 years.
Tell us your domain and we'll check what anyone can see from outside: leaked logins, email security, certificates and exposed services. You get a short summary within 48 hours.
A full scan of your website or app, with a clear report of what's exposed and how to fix it.
Our engineers attack your app the way a real attacker would, and back every finding with proof.
We watch the deep and dark web for your company's names, domains and leaked credentials.
Need several of these? We put them in one proposal for 1 or 3 years, with a discount for the longer commitment.
If you maintain an open-source project or run a non-profit, we can cover you for free or at a reduced price. Just write to us.
Prices exclude VAT. The scope is confirmed with you before we start.