STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to HYCU Protege Security Technical Implementation Guide

V-268258

CAT II (Medium)

The HYCU virtual appliance must obtain its public key certificates from an appropriate certificate policy through an approved service provider.

Rule ID

SV-268258r1039645_rule

STIG

HYCU Protege Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000366CCI-001159CCI-004909

Discussion

For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority will suffice. Satisfies: SRG-APP-000516-NDM-000344, SRG-APP-000910-NDM-000300

Check Content

Open a new HYCU Web UI browser tab and verify there is no warning prompt before proceeding to the Web UI login page. 

If a warning appears in the web browser stating, "Not secure", this is a finding.

Fix Text

Log in to the HYCU Web UI and generate a CSR within the gear menu and "SSL Certificates" menu.
 
Submit this CSR to a DOD PKI authority to have a new certificate created. 

Note: By default, HYCU is configured with a self-signed certificate, but this can be replaced with a DOD-issued certificate. This certificate can be configured by logging in to the HYCU Web UI, navigating to the gear menu and "SSL Certificates" menu, and importing the DOD-issued certificate.