Assessment activity is limited to systems approved by the owner.
Configuration, access paths, certificate handling, and exposed services.
Findings are validated, documented, and routed for remediation.
Public intake address for security reports and research coordination.
About The Lab
Midun Security Lab is a small applied research group focused on practical security assurance for systems that need clear ownership, controlled access, and reliable remediation paths.
What we do
We reproduce security issues, review configuration exposure, examine access control behavior, and produce concise evidence for engineering teams. The goal is not volume; the goal is a defensible finding that can be fixed and verified.
How we work
- Operate only within explicit authorization and defined asset scope.
- Prefer reproducible test cases, clear impact statements, and remediation notes.
- Keep public claims conservative and avoid speculative attribution.
Research Areas
Areas where the lab maintains repeatable review procedures and internal test notes.
Access Control
Authentication boundaries, authorization decisions, session behavior, and administrative access paths.
Identity and policyInfrastructure Exposure
Internet-facing services, certificate configuration, management interfaces, and deployment hygiene.
Edge and servicesVulnerability Validation
Reproduction steps, exploitability checks, impact assessment, and regression verification.
Evidence drivenSecure Connectivity
Controlled connectivity tests, protocol behavior review, and client configuration validation.
Authorized usersResponse Readiness
Issue intake, triage records, remediation tracking, and verification notes for confirmed findings.
Coordinated handlingOperational Review
Change notes, service ownership, exposed asset inventory, and routine configuration evidence.
Reviewable recordsResearch Method
A simple workflow keeps reports understandable, reproducible, and useful to the teams responsible for fixes.
Define scope
Confirm ownership, approved assets, test boundaries, and expected constraints before validation begins.
Validate behavior
Collect reproduction steps, affected versions or paths, supporting evidence, and safety notes.
Assess impact
Separate confirmed risk from assumptions, then document realistic impact and remediation priority.
Verify closure
Review the applied change, confirm the issue no longer reproduces, and keep concise closure notes.
Responsible Disclosure
Reports are handled through a coordinated process so affected owners can understand, reproduce, and remediate issues before public discussion.
Send security reports to contact@midun.eu.org. Include the affected asset, steps to reproduce, expected impact, relevant timestamps, and a safe contact method. Do not perform destructive testing, social engineering, traffic flooding, credential attacks, or testing against third-party systems.
Contact
Use the public contact address for vulnerability reports, authorized research coordination, or questions about Midun-owned assets.