glibc-openssl-fips-hpe

Key Features

Core capabilities and strengths of this container

• FIPS 140-2 validated OpenSSL implementation
• Security-hardened glibc configuration
• HPE enterprise environment optimization
• STIG compliance and hardening measures

Common Use Cases

Typical scenarios where this container excels

• Government and military applications requiring FIPS compliance
• Financial services and healthcare systems
• Secure enterprise application deployments
• High-security containerized environments

Pull Latest Image

Download the container image from the registry

Basic Run

Run the container with basic configuration

docker run -it --name glibc-openssl-fips-hpe-test clnstrt-images.cleanstart.com/$ORGANIZATION/glibc-openssl-fips-hpe:latest-dev

Production Deployment

Deploy with production security settings

docker run -d --name glibc-openssl-fips-hpe-prod \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  clnstrt-images.cleanstart.com/$ORGANIZATION/glibc-openssl-fips-hpe:latest

Volume Mount

Mount local directory for persistent data

docker run -v $(pwd)/data:/data clnstrt-images.cleanstart.com/$ORGANIZATION/glibc-openssl-fips-hpe:latest

Port Forwarding

Run with custom port mappings

docker run -p 8080:80 clnstrt-images.cleanstart.com/$ORGANIZATION/glibc-openssl-fips-hpe:latest

Environment Variables

Configuration options available through environment variables

• | Variable | Default | Description | |----------|---------|-------------| | FIPS_MODE | enabled | FIPS mode status | | OPENSSL_FIPS | 1 | OpenSSL FIPS mode | | GLIBC_TUNABLES | glibc.malloc.mxfast=0 | Glibc security tuning | | SSL_CERT_DIR | /etc/ssl/certs | SSL certificates directory |

Security Best Practices

Recommended security configurations and practices

• Verify FIPS mode is enabled using openssl engine command
• Implement strict access controls and user permissions
• Regular security audits and compliance checks
• Monitor cryptographic operations for FIPS compliance
• Maintain up-to-date security patches
• Use secure communication protocols

Kubernetes Security Context

Recommended security context for Kubernetes deployments

securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  runAsGroup: 1000
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]
  seccompProfile:
    type: RuntimeDefault

Documentation Resources

Essential links and resources for further information

• Container Registry: https://clnstrt-images.cleanstart.com/$ORGANIZATION
• FIPS 140-2 Documentation: https://csrc.nist.gov/publications/detail/fips/140/2/final
• OpenSSL FIPS Guide: https://www.openssl.org/docs/fips.html