Previous Topic

Next Topic

Book Contents

Book Index

Instant Messaging Traffic

SmartDefense can block instant messaging applications that use VoIP protocols, by identifying the messaging application's fingerprints and HTTP headers.

This category includes the following nodes:

 

Note: SmartDefense can detect instant messaging traffic regardless of the TCP port being used to initiate the session.

 

Note: Skype versions up to 2.0.0.103 are supported.

In each node, you can configure how instant messaging connections of the selected type should be handled, using the following table.

Instant Messengers Fields

In this field…

Do this…

Action

Specify what action to take when a connection is attempted, by selecting one of the following:

  • Block. Block the connection.
  • None. No action. This is the default.

Track

Specify whether to log instant messenger connections, by selecting one of the following:

  • Log. Log the connection.
  • None. Do not log the connection. This is the default.

Block proprietary protocol /
Block proprietary protocols on all ports

Specify whether proprietary protocols should be blocked on all ports, by selecting one of the following:

  • Block. Block the proprietary protocol on all ports. This in effect prevents all communication using this instant messenger application. This is the default.
  • None. Do not block the proprietary protocol on all ports.

Block masquerading over HTTP protocol

Specify whether to block using the instant messenger application over HTTP, by selecting one of the following:

  • Block. Block using the application over HTTP. This is the default.
  • None. Do not block using the application over HTTP.

See Also

SmartDefense Categories

Denial of Service

IP and ICMP

TCP

Port Scan

FTP

HTTP

Microsoft Networks

IGMP

VoIP

Peer-to-Peer

Games