VMware VCM 5.3 - CONFIGURATION MANAGER SECURITY ENVIRONMENT REQUIREMENTS Uživatelský manuál Strana 13

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 32
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 12
vCenter Configuration Manager Security Environment Requirements
TECHNICAL WHITE PAPER / 13
5.0 Personnel Selection and Training
5.1 VCM accounts are granted to users who are trusted, trained, and qualified as sys-
tem and network administrators
VCM is an Enterprise-wide configuration management and compliance tool. It is unsurpassed in its ability to collect,
correlate and change system data on managed machines in the enterprise. VCM can configure security policies,
collect and aggregate confidential information, install software and patches, and generally act as an administrative
interface to an entire network of machines. This power of VCM is intended for use by trusted users that are as
responsible as system and network administrators. The users must use the tool responsibly and protect their access
from being subverted for unauthorized uses. In particular, VCM administrators should avoid assigning entire domain
groups to VCM logins and should set the Windows login restrictions and password policies for user accounts that are
VCM logins to values consistent with administrator accounts.
5.2 VCM users are advised to treat direct login prompts to VCM with skepticism and
caution
When a user logs into Windows using a domain account known to VCM and then connects to VCM, the system can
authorize the user by their Windows identity rather than requiring them to login explicitly to VCM. This leveraging of the
Windows login system resists spoofing and cross-site scripting attacks that exploit the IE browser. VCM also accepts
browser-based login when the Windows identity is either unavailable or not recognized by VCM. While this latter
approach is possible, the best practice is to login (or runas) using a domain account, configure IE to transmit the login
credentials, and treat browser-based login prompts with skepticism and caution.
5.3 VCMusers must protect collected data as confidential information
The results of a VCM collection can contain infrastructure configuration settings, password and credential policies,
encrypted password file entries, and any file uploaded from the managed machine. Even if this data is not confidential
to the managed machine, it may be confidential to the machine's users. Without explicit knowledge of what is or is not
sensitive, VCM users should treat and protect all collection results as confidential. Collected data should not be stored
on public shares or in directories accessible to other users, including other VCM users since they may not have
collection rights against the machine being the origin of the data.
5.4 Trust individual collectionresults nomore than their source
Data collected by VCM is returned by the agent running on the managed machine. This Agent, while usually protected
from tampering by non-administrative users, is ultimately subject to modification and tampering by the machine
administrator or a malware infection. For this reason collected data should never be trusted more than the trust in the
integrity of the source. Consider making decisions based on aggregate values rather than individual ones: how many
machines have a vulnerability rather than the compliance state of a specific machine.
Zobrazit stránku 12
1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 31 32

Komentáře k této Příručce

Žádné komentáře