myOwnCA By EnigmaIS

MYOWNCA / DOCUMENTATION

Use cases

Practical ways to use private certificates for services, devices, and people.

Services: Your apps deserve another layer of protection.

Exposing a dashboard, home server, or business application through a tunnel? Even trusted third-party software can have vulnerabilities. Add defense in depth: require a trusted client certificate at a compatible access gateway before requests reach your application. Issue and manage those certificates with myOwnCA.

Services workflow
  1. 01Client certificate
  2. 02Access check
  3. 03Private app

What you need: Your access gateway must support and enforce client-certificate authentication at the visitor’s TLS connection.

Devices: From the shelf to a trusted connection.

Preparing payment terminals or kiosks for deployment? Give each compatible device its own certificate during staging. When it connects after storage, your provisioning service can verify that identity before releasing configuration.

Devices workflow
  1. 01Device request
  2. 02Certificate issued
  3. 03Identity verified

What you need: Requires device and provisioning software that support certificate authentication.

People: Make your team’s email verifiable.

Help colleagues verify who sent a message and whether it changed in transit. Issue individual S/MIME certificates with myOwnCA and use them to sign email in compatible mail clients.

People workflow
  1. 01Personal certificate
  2. 02Signed email
  3. 03Verified signature

What you need: Recipients’ mail clients must trust your organization’s CA to verify the signature’s certificate.

For configuration examples, see the Nginx, Apache, and homelab guides.

Planning a deployment?

Talk to EnigmaIS