Home
Deployment guide
Learn how to install and connect your Security Center SaaS application.
Requirements
Port requirements
To enable communication with cameras, appliances, clients, and on-premises Security Center systems, you must open specific network ports.
Port requirements for clients
To enable communication with clients, you must open specific network ports.

Deployment guide
Learn how to install and connect your Security Center SaaS application.
- Getting started
- Requirements
  - Presale checklist
    Use this checklist to collect information about the customer's environment and to ensure that it meets Security Center SaaS requirements.
  - Network requirements
    To successfully deploy Security Center SaaS in the cloud, network infrastructure must meet the required performance criteria, and network policy must adhere to the setup recommendations.
  - Port requirements
    To enable communication with cameras, appliances, clients, and on-premises Security Center systems, you must open specific network ports.
    - Port requirements for direct-to-cloud cameras
      To enable communication with direct-to-cloud (D2C) cameras, you must open specific outbound ports for the associated domains.
    - Port requirements for appliances
      To enable communication with appliances, you must open specific network ports.
    - Port requirements for clients
      To enable communication with clients, you must open specific network ports.
    - Port requirements for Federation
      For Federation™ of on-premises Security Center systems into Security Center SaaS, you must open firewall ports to allow communication between the sites.
- User management
- Device management
- Federation through reverse tunneling
User guide
Learn about Security Center SaaS.
Genetec ClearID User Guide
Learn how to set up and use ClearID in Security Center SaaS.
Additional resources
Review the supported device list and other resources.
Glossary

Port requirements for clients

2024-06-19

To enable communication with clients, you must open specific network ports.

The following ports must be open for the associated domains, so the client can connect to cloud services, select the correct organization, and authenticate.


Outbound port	Endpoint domain	Port usage
Web clients
TCP 443	securitycentersaas.genetec.cloud us.securitycentersaas.genetec.cloud	Security Center SaaS Web Services
	login.genetec.com id.login.genetec.com assets.login.genetec.com challenges.cloudflare.com	Genetec™ single sign-on (SSO)
	login.microsoftonline.com aadcdn.msauth.net login.live.com	Genetec™ single sign-on (SSO)
	events.launchdarkly.com app.launchdarkly.com clientstream.launchdarkly.com	Genetec features management
	sgnlr-uni-prodglobal-eastus2.service.signalr.net canadacentral-1.in.applicationinsights.azure.com	Monitoring & eventing
	az416426.vo.msecnd.net dc.services.visualstudio.com widget.intercom.io js.intercomcdn.com	Dependencies
Genetec™ Operation web and mobile applications
TCP 443	*.gsc-cloud.com a.tile.openstreetmap.org b.tile.openstreetmap.org	HTTPS port
Genetec™ Configuration web
TCP 443	eastus2.video.genetec.cloud	HTTPS port for video operations
Genetec Operation and Genetec Configuration desktop applications
TCP 5500	*.gsc-cloud.com	Genetec Security Center TLS proxy
TCP 554 TCP 560	*.gsc-cloud.com	RTSP port (over TLS)
TCP 960	*.gsc-cloud.com	Live and playback stream requests
TCP 443	downloadcenter1.genetec.com	HTTPS