Security testing and hardening, from finding the exposure to closing it.

Orygn works both sides of security. It tests web applications, cloud environments, identity systems, and APIs the way an attacker would, then fixes what that testing turns up, so findings get closed instead of filed away. Orygn works across the Houston area and remotely.

What the work covers

Testing that reflects how the system is actually built, followed by the fixes.

Penetration testing

Manual, adversarial testing of web applications, APIs, cloud environments, and identity systems. The goal is to find what an attacker could actually reach and do, not to forward a scanner report with the defaults left on.

Vulnerability assessment

Mapping where the real exposure sits, separating the findings that matter from the noise, and ranking them by what is reachable and what it would cost if it were exploited.

Identity and access review

Over-broad roles, risky OAuth consent grants, stale and orphaned accounts, and expiring service credentials, with a particular depth in Microsoft Entra ID.

Hardening and remediation

Closing what the testing turns up: access controls, server and cloud configuration, TLS and security headers, dependency versions, and risky defaults. See security hardening for the full scope.

How an engagement runs

Authorized and scoped first. Then tested, reproduced, fixed, and re-tested.

01

Written authorization and an agreed scope

Testing starts only after the system owner signs off on what is in scope, what is out, and when testing happens. Orygn tests only systems it owns or has written permission to test.

02

Testing and verified findings

Each finding comes with the steps to reproduce it and an honest read on its real-world impact, so the system owner can tell a critical issue from a theoretical one.

03

Remediation and re-test

Because Orygn also does the fixing, findings get closed and then checked again, rather than handed over as a report for someone else to work through.

Security tools Orygn has built

The scanners and auditors behind the work, several of them open source.

WebShield

A production security scanner covering transport, network, and application layers: security headers, TLS, CVEs through OSV.dev, DNS and email authentication, exposed paths, and tech fingerprinting.

See WebShield

Entra OAuth Consent Auditor

An open-source CLI that finds risky and illicit OAuth consent grants in Microsoft Entra ID tenants.

See the auditor

Entra Credential Sentinel and Zombie Account Hunter

Two open-source CLIs for Entra ID: one tracks expiring service principal credentials, the other finds inactive accounts and unused licenses.

See Zombie Account Hunter

CI Evidence Pack

An open-source CLI that produces tamper-evident evidence packages from CI/CD pipelines, for supply-chain integrity.

See CI Evidence Pack

Published security research

Original security research, published with DOIs.

From Hallucination to Registration

A software supply-chain study of slopsquatting. Five code models invented 1,641 distinct package names that do not exist on npm or PyPI, and the install-time code-execution step was confirmed in a sealed offline lab using a benign package.

Read the study

The Recipe Is the Fingerprint

A privacy and forensics study showing that the generation recipe AI image tools write into every PNG by default identifies a single creator from one image 55.8 percent of the time. Disclosed to the tool developers and platform before publication.

Read the study

FAQ

Common questions about security testing.

Yes. Orygn tests web applications, cloud environments, identity systems, and APIs the way an attacker would, then works through the findings and fixes them.
Written authorization from the system owner and an agreed scope. Orygn only tests systems it owns or has written permission to test.
Yes. Orygn does the remediation as well as the testing, so findings get closed and re-tested rather than handed off as a report.

Next step

Start with the system and what has you concerned about it.

That is enough to agree on a scope, the authorization needed, and the right first step. For security matters, email security@orygn.tech.

Get in touch