Cisco Cisco Web Security Appliance S360 ユーザーガイド
3 © 2010 Cisco and/or its affiliates. All rights reserved.
Note
If you block Facebook General, it
is the same as blocking the entire
Facebook application type.
Controlling Facebook Activity
Understanding Facebook General
Any area of Facebook.com that is not explicitly covered under one of the native
Facebook applications is covered under the “Facebook General” native application.
This includes users’ Wall and Profile pages, for example.
Facebook applications is covered under the “Facebook General” native application.
This includes users’ Wall and Profile pages, for example.
Some Facebook objects that are included in a native Facebook application, such
as photographs in Facebook Photos, might also appear on a user’s Wall. When
users view their Walls, access to objects on the Wall is determined by the settings
configured for the Facebook General application. For example, if you configure the
Block Like/Tag behavior control for Facebook Photos, but not for Facebook General,
users can click the Like link for photos from their Wall, but not from a photo album.
as photographs in Facebook Photos, might also appear on a user’s Wall. When
users view their Walls, access to objects on the Wall is determined by the settings
configured for the Facebook General application. For example, if you configure the
Block Like/Tag behavior control for Facebook Photos, but not for Facebook General,
users can click the Like link for photos from their Wall, but not from a photo album.
However, bandwidth controls always apply to videos, even if they appear on a
user’s Wall.
user’s Wall.
User Experience when Accessing Facebook
When you block a Facebook application or application behavior, users are prevented
from performing the intended action, but it is not always clear to users that their
actions are explicitly being blocked by the Web Security appliance. When the AVC
engine blocks Facebook content, it sends an end-user notification page by default.
However, due to how Facebook displays content in the web browser, it quite often
does not show the end-user notification page.
from performing the intended action, but it is not always clear to users that their
actions are explicitly being blocked by the Web Security appliance. When the AVC
engine blocks Facebook content, it sends an end-user notification page by default.
However, due to how Facebook displays content in the web browser, it quite often
does not show the end-user notification page.
Additionally, there are multiple ways to accomplish most tasks in Facebook. For
example, users can reach a page to upload photos using different paths. Users
trying to access blocked Facebook content may observe different responses
depending on the application they are accessing, the path used to reach the
application, and how the applicable Access Policy is configured to handle the
application and application behaviors.
example, users can reach a page to upload photos using different paths. Users
trying to access blocked Facebook content may observe different responses
depending on the application they are accessing, the path used to reach the
application, and how the applicable Access Policy is configured to handle the
application and application behaviors.
The following list summarizes the types of responses users might observe based on
which applications and application behaviors are blocked:
which applications and application behaviors are blocked:
• Block external Facebook application. Users are prevented from navigating to
the external Facebook application webpage. Facebook displays a generic error
message.
message.
• Block native Facebook application. Users cannot navigate to any page dedicated
to that application. For example, if you block Facebook Photos, users cannot
navigate to the page where they click a link to upload photos to an album.
Facebook displays a generic error message.
navigate to the page where they click a link to upload photos to an album.
Facebook displays a generic error message.
• Block native Facebook application behavior. Users might observe any of the
following behaviors:
– The user’s request is silently ignored. This typically occurs when the user
clicks a link or button and expects something to happen, but nothing happens.
For example, this might occur when the user tries to cancel an event, delete a
comment, or tag a person in a photo.
For example, this might occur when the user tries to cancel an event, delete a
comment, or tag a person in a photo.