Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

FAQ: What to use as "common name" for HTTPS CSR

Expand / Collapse


This article applies to:

  • SWG 10.x 11.x

Question:

  • I want to use our local PKI infrastructure to generate a certificate. The CSR request form requires a Common Name and I'm not sure what to use as common name. Normal procedure is to use the FQDN of the website or the servername for server certificates. What should I use for HTTPS certificate?

Reply:

It should be enough to make it someDomain.com. No need for the host name part.
Essentially it doesn't matter what you put there. Eventuallyyou will have to import it to the end users to avoid the https warningmessages.



To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.