[ PRJ-002 ] · 2025
Secure access platform
A cybersecurity-focused platform for managing industrial machines, credentials and sensitive configurations through cryptographic protection, controlled access and auditable workflows.
- Role
- Full-stack & cybersecurity engineer, from cryptographic architecture to operator interface
- Layers
- [02] PROTECT[03] BUILD[04] THINK
- Stack
- C# · .NET · Vue · SQL · OpenAPI · AES · RSA · ECC · X.509 · TPM · Digital signatures · Envelope encryption · Key wrapping
Context
Industrial machines required centralized management of credentials, software configurations, users and operational requests without exposing sensitive information across applications, databases or administrative workflows.
The challenge was not simply storing machine data, but defining how secrets were generated, protected, exchanged and accessed throughout their lifecycle.
What I built
- Cryptographic architecture: designed application-level protection for sensitive machine data using symmetric and asymmetric cryptographic primitives according to the type and lifecycle of each secret.
- Key management: separated encrypted data from the cryptographic material required to access it, reducing the impact of database or application-layer compromise.
- Hardware-backed security: integrated hardware-protected key operations and trusted key storage to reduce exposure of high-value cryptographic material.
- Credential lifecycle: implemented secure generation, storage and retrieval of machine credentials and password policies, with sensitive information cryptographically protected and plaintext restricted to non-sensitive data.
- Access control: modeled users, roles and authorization boundaries around security-sensitive operations and machine resources.
- Secure API layer: developed .NET REST services with validation, controlled resource exposure, optimistic concurrency and explicit handling of sensitive entities.
- Contract-driven frontend: used OpenAPI-generated TypeScript contracts to keep security-sensitive frontend and backend operations aligned as the platform evolved.
- Auditability & consistency: structured operations so changes to critical machine information could be tracked and conflicting updates could not silently overwrite one another.
Outcome
A centralized security layer for machine-related credentials and configurations, replacing scattered handling of sensitive information with controlled cryptographic workflows.
The platform made security part of the application architecture itself rather than an additional protection layer applied after the system had already been designed.