User`s manual
35
AXIS 240Q - System Options
HTTPS
For greater security, the AXIS 240Q can be configured to use HTTPS (Hypertext Transfer
Protocol over SSL (Secure Socket Layer)). That is, all communication that would otherwise
go via HTTP instead goes via an encrypted HTTPS connection.
Certificate
- to use HTTPS for communication with the AXIS 240Q, a Certificate must be
created using one of these methods:
• A self-signed certificate can be created in the
video server, but this does not guarantee
the same level of security as an official certificate.
• An official certificate issued by a CA (Certificat
e Authority). A CA issues and manages
security credentials and public keys for message encryption.
1. Click either Crea
te self-signed certificate or Create Certificate Request and enter
the required information in the provided fields
2. Click OK.
3. Create self-signed certificate generates and installs a certificate which will be
displayed under Installed Certificate.
Create Certificate Request generates a PEM formatted request which you copy
and send to a CA for signing. When the signed certificate is returned, click Install
signed certificate... to install the certificate in the AXIS 240Q.
4. Set the HTTPS Connection Policy for the administrator, Operator and Viewer to
enable HTTPS connection (set to HTTP by default)
Please refer to the home page of your preferre
d CA for information on where to send the
request etc. For more information, please see the online help
802.1x - Network Admission Control
IEEE 802.1x is an IEEE standard for port-based Network Admission Control. It provides
authentication to devices attached to a network port (wired or wireless), establishing a
point-to-point connection, or, if authentication fails, preventing access on that port.
802.1x is based on EAP (Extensible Authentication Protocol).
In a 802.1x enabled network switc
h, clients equipped with the correct software can be
authenticated and allowed or denied network access at the Ethernet level.
Clients and servers in an 802.1x network may
need to authenticate each other by some
means. In the Axis implementation this is done with the help of digital certificates
provided by a Certification Authority. These are then validated by a third-party entity,
such as a RADIUS server, examples of which are Free Radius and Microsoft Internet
Authentication Service.