SimpleHelp Enterprise

FIPS support for
SimpleHelp Enterprise

SimpleHelp Enterprise combines Bouncy Castle Java FIPS cryptography with an enforced security policy, deployment checks and tools for ongoing verification. Administrators can inspect the server's cryptographic configuration, identify settings that require attention and retain evidence for security reviews.

A dedicated Enterprise distribution

The FIPS feature set is available exclusively with SimpleHelp Enterprise. It requires the dedicated FIPS distribution. Installing a standard SimpleHelp release with an Enterprise licence does not activate FIPS mode.

Once you have a valid Enterprise license, sign in to your SimpleHelp account and open the Enterprise section to download the FIPS build.

Controls and validation coverage

FIPS Status checks the health of the implemented controls. The current release declaration records formal validation coverage as “not established” for the exact SimpleHelp build, module version and operating environment.

Understand validation coverage

Built on Bouncy Castle FIPS

Bouncy Castle provides cryptographic libraries for encryption, digital signatures, hashing, certificates and secure communications. SimpleHelp's FIPS distribution uses the Bouncy Castle FIPS Java API (BC-FJA) as its cryptographic foundation, together with Bouncy Castle's FIPS-compatible TLS and certificate support libraries. The official Java FIPS overview and release notes describe these components.

Within SimpleHelp, BCFIPS supplies the core cryptographic provider and approved random number generation. BCJSSE, supplied by bctls-fips, provides the Java TLS integration and is configured to use BCFIPS. SimpleHelp adds the enforced configuration policy, startup verification, readiness checks, monitoring and evidence reporting described below.

For technical background, see Bouncy Castle's official resources:

How the implementation works

The FIPS distribution configures the Bouncy Castle FIPS provider in approved-only mode and uses the FIPS-configured Bouncy Castle JSSE provider for server TLS. It applies a defined policy to the cryptographic runtime, inbound TLS, certificates and authentication configuration.

Before opening its normal network listeners, the server verifies its core runtime controls. If those checks fail, startup is blocked and the server logs the failure for investigation.

Enforced security policy
AreaCurrent implementation
Cryptographic providerBCFIPS must be first in the Java security provider order, with approved-only mode active.
Random number generationThe configured server random source must use the BCFIPS approved deterministic random bit generator (DRBG).
TLS providerBCJSSE must be configured for BCFIPS, appear second in provider order and supply the active server TLS context.
TLS protocolsInbound TLS is restricted to TLS 1.2 and TLS 1.3.
TLS encryptionThe permitted cipher suites use AES-128-GCM or AES-256-GCM. TLS 1.2 suites require ECDHE key exchange for forward secrecy.
TLS named groupsThe policy permits the NIST curves secp256r1, secp384r1 and secp521r1.
Certificate policyActive certificates are checked for validity dates, supported key types and sizes, and permitted signature algorithms. RSA keys must be at least 2048 bits; supported EC keys must be at least 256 bits. Certificates outside the policy are rejected when activated.
Local passwordsCurrent password records use salted PBKDF2-HMAC-SHA-512 with 150,000 iterations. FIPS mode enforces a minimum of 14 characters; administrators can require longer passwords. Legacy records are identified for migration.
Directory authenticationLDAP and Active Directory connections must use TLS. The FIPS build rejects enabled LDAP providers configured without TLS.
RADIUSRADIUS cannot be enabled in the FIPS build because its packet authentication relies on MD5.

The effective TLS protocols and cipher suites are enforced by the connected FIPS server and shown as read-only in Administration. Older saved settings cannot enable protocols or cipher suites outside the policy.

Cryptographic components

The implementation described here uses these Bouncy Castle components. Confirm the versions in your release before deployment:

Cryptographic components
ComponentVersionPurpose
bc-fips2.1.2Core cryptographic provider
bctls-fips2.1.24TLS and JSSE support
bcpkix-fips2.1.12Certificate and PKIX support
bcutil-fips2.1.7Supporting utilities

The FIPS Status report records component versions observed at runtime and SHA-256 hashes where component files are available. Use the report from your installation when recording the identity of a deployed release.

Verify, monitor and report

FIPS Status dashboard

Open Administration > FIPS > FIPS Status to inspect the connected server. The page presents the overall state, the last verification time and individual results covering the cryptographic runtime, TLS, certificates, credentials and authentication providers. Technical details include server and environment identity, component information, public certificate evidence and the observed key-storage backend.

The status comes from the server. Administrators can select Run Verification to request a fresh assessment and use remediation actions to open the relevant configuration pages.

FIPS Status results
StatusMeaning
FIPS Controls ActiveThe assessed runtime and deployment controls pass. Validation coverage and informational checks remain separately reported.
Action RequiredOne or more deployment checks need attention, such as legacy password records, an incompatible authentication provider or a certificate outside the policy.
Runtime Verification FailedA core cryptographic runtime control failed verification.
Standard Build / FIPS ReadinessThe server is running the standard distribution and can be reviewed for migration requirements.
Status UnavailableA report could not be obtained. A healthy state is not inferred.

FIPS findings also appear in Security Audit. Snoozing or ignoring an audit reminder does not remove the underlying finding from the FIPS assessment or change its overall state.

Readiness checks before migration

Enterprise administrators running a standard build can review FIPS readiness before changing distributions. These checks identify deployment settings that need attention, including legacy technician password records, certificate policy issues and incompatible authentication providers.

The page also provides an action to set password requirements for credential migration. Reset affected local passwords before switching to FIPS, ensuring they meet the 14-character minimum or your higher configured minimum. A readiness report does not activate the FIPS runtime.

Exportable evidence

Use Export Report to save a human-readable PDF of the FIPS assessment. A machine-readable JSON report is available through the status API for monitoring and evidence collection.

Both formats include the verification timestamp, server and environment identity, available component versions and hashes, effective TLS settings, public certificate information and operational check results. The JSON report additionally includes the release's validation-coverage statement. These reports provide point-in-time evidence and are not signed attestations.

Monitoring, events and notifications

The server reassesses FIPS status every five minutes. Changes to the overall state or check results generate a FIPS Status Changed event. Runtime failures and newly detected deployment actions also produce administrator notifications.

Monitoring systems can retrieve the assessment using an API token with Configure server permission:

GET /api/v1/server/fips-status/get
Authorization: Bearer <token>

Evaluate the report's overallState as well as the HTTP result. A successful request can return a report containing ACTION_REQUIRED or RUNTIME_FAILURE. Treat UNAVAILABLE as an unknown state that requires investigation.

Migration and update safeguards

SimpleHelp supports migration from a standard installation to the FIPS distribution. The installation then requires FIPS releases for subsequent updates and uses a dedicated FIPS update channel.

The Windows FIPS installer requires explicit confirmation before converting a standard installation. Silent migration requires /ACCEPTFIPSMIGRATION alongside /S. Current standard installers and servers include safeguards against replacing or opening a FIPS installation with a standard build.

Migration is one-way within the same installation. To return to a standard deployment, restore a complete pre-migration backup into a separate installation. Backups taken after migration require a FIPS build.

Preparing your deployment

  1. Confirm that you have a SimpleHelp Enterprise licence and obtain the dedicated FIPS release.
  2. Review FIPS readiness on your existing server. For configurations originating before 6.4.0, first run the current standard build and save the configuration to complete the required configuration migration.
  3. Reset affected local passwords, replace legacy password records and apply a minimum password length of at least 14 characters.
  4. Replace RADIUS authentication and enable TLS for every LDAP or Active Directory provider.
  5. Install certificates and chains that meet the FIPS certificate policy.
  6. Stop the server and retain a complete pre-migration backup, including configuration, certificates, keys and the exact standard release.
  7. Install the FIPS distribution, run verification, resolve deployment findings and retain the evidence report with your deployment records.
  8. Continue using FIPS releases for updates and monitor the installation's status.

Understanding validation coverage

SimpleHelp's FIPS Status assessment verifies the implemented runtime and deployment controls. Formal FIPS 140 validation coverage depends on the exact cryptographic module, release artifacts, operating environment and applicable validation evidence.

Bouncy Castle publishes its module validation information through its Java FIPS release page, including a link to NIST CMVP certificate #4943. That record describes the Bouncy Castle module's validation scope. Its applicability to a particular SimpleHelp release must be established using the exact module version and deployment environment.

The current release declaration records validation coverage as “not established” for the exact SimpleHelp build, module version and operating environment. A “FIPS Controls Active” result reports the health of the assessed controls; it does not establish FIPS 140 validation of SimpleHelp as a product or of the complete deployment.

The report describes the observed key-storage backend, while private-key protection at rest and external hardware security module assurance remain outside its assessment. The server assessment also does not certify every client, integration or cryptographic operation across an organisation's deployment.

Use the release-specific evidence and your organisation's requirements when assessing deployment suitability. The SimpleHelp team can help identify the relevant release and deployment information.

Plan your FIPS deployment

The FIPS distribution and associated feature set are exclusive to SimpleHelp Enterprise. With a valid Enterprise license, you can download the FIPS build from the Enterprise section of your SimpleHelp account. Talk to us about your requirements and deployment plan.

Contact SimpleHelp