Information Security Policy
Information Security Policy
Acceptable Use
INFORMATION
Access Management SECURITY POLICY
Backup and Restoration The Information Security Policy is designed
to protect and preserve the appropriate
Change Management confidentiality, integrity, and availability of
information and information systems owned by
or in the care of the Company and its subsidiaries,
Compliance affiliates, and service providers. This Policy
identifies and describes the principles that Hilton
Device Management requires to globally protect company information
and company information assets using industry
best practices with a risk-based and business
Encryption aware approach.
Vendor Management
Definitions
• The Company reserves the right to audit Company • Network monitoring, port scanning, or security/
resources at any time to ensure compliance with vulnerability scanning, including the ‘testing’ of
this policy. security tools on any Company resources without
• Users, including support personnel and service authorization;
providers, must be explicitly authorized to use • Circumventing user authentication or Company
Company information assets. Assignment of a information security controls;
device to a user and / or granting logical access to • Installing or circumventing software with the direct
a device or service in accordance with the Access or indirect result of avoiding information security
Management section of this policy constitutes services and restrictions at Company;
explicit authorization. • Providing confidential information about or lists
• Users, including support personnel and service of Company guests, clients, service providers, or
providers, may use Company equipment and / or candidates to parties outside Company without
networks during non-working time for transmitting prior authorization from Company Senior
personal messages and / or Internet browsing, so Management and only as permissible and in
long as such use does not interfere with the user’s compliance with applicable law;
or other users’ personal job responsibilities, unduly • Violating copyright, trade secret, patent, or other
impact the operation of the Company computer intellectual property rights or similar laws or
network, or otherwise violate any other provisions of regulations. This includes, but is not limited to, the
this policy. installation or distribution of “pirated” or other
software products that are not appropriately
B. Prohibited Activities licensed for use by Company;
Company Team Members must not engage in any • Copying copyrighted material including, but
activity that is unlawful under local, state, federal, not limited to, digitization and distribution of
or international law while utilizing Company-owned photographs from magazines, books, or other
resources. copyrighted sources; copyrighted music; and the
installation of any copyrighted software for which
The following activities are considered by the Company does not have an active license; and
Company, at a minimum, to be categorized as • Exporting software, technical information,
unacceptable use and are strictly prohibited: encryption software, or technology in violation
• Introducing or downloading malicious programs of international or regional export control laws.
onto Company technology resources (e.g., viruses, Exceptions must be preapproved by Information
worms, Trojan Horses, email bombs, malware); Security & Compliance to export any questionable
• Using Company technology resources to advertise material.
or sell products, items, or services for personal gain;
• Breaching or disrupting network communications. C. Prohibited Electronic Communication Activities
Security breaches and disruptions include, but are The following activities are strictly prohibited when
not limited to: using Company information technology resources:
• Knowingly accessing information for which the • Using Company equipment and / or networks for
user is not an intended recipient; non-business-related activities during working
• Logging into a server or account that the user is times, with the exception of incidental and
not expressly authorized to access; occasional personal messages or Internet usage.
• Generating excessive network traffic or causing • Transmitting or accessing by email or other form
any type of denial-of-service condition; of electronic communication any material that
• Performing network reconnaissance and analysis is profane, obscene, sexually explicit, or offensive
activities without authorization (e.g., network based on any protected characteristic (e.g., sexual
sniffing); and comments or images, racial or ethnic slurs,
• Introducing malformed or malicious network comments that may be offensive on the basis of
traffic (e.g., ping floods, packet smooth, forging an individual’s age, religious or political belief, sex,
routing information); disability, or any other status protected by law) or any
other such conduct that may violate the law
• User accounts granted system administration • Changes to user access and/or roles must follow
privileges must only be used for administration the same approval requirements as user accounts
purposes. Accounts granted administrative-level identified in Section A.
access privileges must not be used for general use • Assignment of access must correlate with approval
(e.g., reading email, Internet browsing). records.
• User accounts temporarily assigned to vendors for • RBAC must be implemented through automated
maintenance purposes must only be activated as access control systems; the Company will maintain
needed and be disabled when not in use. and support technology to provide information
• System and service account passwords must be access controls, secure configurations that support
changed from vendor defaults and are subject to strong access control, and implement applications
the Access Management Standard. that enable implementation of RBAC based on the
• User accounts granted to contractors, consultants, principle of least privilege.
and/or temporary employees must automatically
expire after a period of time as defined in the F. Access Removals
Access Management Standard. Reactivation of the • Human Resources must immediately notify User
account must be approved. Account Administrators responsible for physical
access and logical access of job terminations and
D. Access Requests job transfers.
• Access must be requested using the principle of • Physical access and logical access to each
least privilege, whereby users are assigned only system, application, or database must be disabled
those permissions consistent with their job title, immediately following a job termination or job
classification, or function. Permissions are not to be transfer notification.
granted functionality based on a “copy” of another
user account with similar job responsibilities. G. Authentication and Passwords
Authentication and Password systems are
E. Access Assignments implemented by and the responsibility of Information
Access assignment is performed by and the Technology or an authorized service provider. Any
responsibility of Information Technology or an other authentication or password systems used in
authorized service provider. the Company environment must be pre-approved
• Permissions must be assigned using a Role Base by Information Technology and compliant with the
Access Control (RBAC) model that implements Information Security Policy.
the principle of least privilege, whereby users are • Access control systems must require both a user
assigned only those permissions consistent with account as well as at least one other method to
their job title, classification, or function. Permissions authenticate the user (e.g., password, token).
are not to be granted functionality based on a • Passwords must be securely delivered to any user
“copy” of another user account with similar job and kept secured at all times.
responsibilities. • Passwords must change upon initial logon, system
• RBAC records must be defined, documented, and permitting, by the user and subsequently changed
maintained, including: every 90 days.
• Access roles (e.g., groups, profiles) and their • After six unsuccessful password attempts, the
associated system functionality; device (not including mobile phones or tablets) must
• A RBAC “matrix” or similar model that associates be made unavailable to the user via account locking,
roles with job titles, classifications, or functions; keyboard locking, and/or screen blanking for at least
and 30 minutes or until an administrator unlocks the
• Roles that introduce separation of duties issues user’s account.
when assigned to the same user. • After ten unsuccessful password attempts,
• Transferring to a different job function must trigger Blackberry, iPhone, iPad, and Android devices will be
a review of current user access. If access needs disabled and erased.
to be modified, it must follow the same approval
requirements as identified in Section A.
• Passwords must never be stored electronically • For data centers and computer rooms, an offsite
in plain text (e.g., in computer files, on computing copy of data must be kept to help ensure the
devices, on smart phones). recoverability of data in the event of a physical
• Sharing of passwords to individual user accounts is disaster at the primary location.
prohibited. • Physical backup media (e.g., backup tapes) must
• Passwords must comply with the following rules and be subject to management processes that include
contain: labeling (barcoding), location tracking, and periodic
• a minimum of seven characters; inventory.
• alpha-numeric characters; • Physical backup media must be secured when
• a minimum of one special character (e.g., !, #, $, %) in transit between Company or non-Company
(system permitting); and locations.
• upper and lower case letters (system permitting). • Transmittal records must be retained when physical
• Passwords for mobile phones and tablets must backup media is sent offsite or returned to site.
comply with the following rules and contain: • A security review of the facility where physical
• a minimum of five characters. backup media are stored must be performed at
• Passwords must not: least annually.
• repeat any of the four most recently used • Laptops must have Company online backup
passwords; software installed.
• use standalone words from a dictionary, the
movies, or geographical locations; B. Restoration
• use month, day, year combinations (e.g., Jan07, Restoration of protected information must be
07Jan13, Jan2013); and tested semi-annually to ensure the information
• contain proper names (e.g., oneself, family, friends, is recoverable and complete in the event of an
colleagues, vendors). information loss.
• A user’s identity must be positively verified before a
request to reset the user’s password is performed. C. Business Continuity
Business process and data owners must define and
are responsible for maintaining a risk-based business
BACKUP AND RESTORATION continuity plan.
• The business continuity plan must be maintained
Backup and Restoration management protects to ensure critical business functions are available as
Company information from intentional or needed.
accidental loss and ensures timely restoration of • The business continuity plan must define recovery
the information. timeframes and prioritize resumption of functions
as prioritized by the business.
• The business continuity plan must be tested at least
A. Backups once annually and maintained by annual reviews,
Backups are performed by and the responsibility of unless increased frequency is required in order to
Information Technology or an authorized service meet legal, regulatory, or compliance standards
provider, as well as authorized Team Members at the applicable to the Company (e.g., PCI DSS, Sarbanes-
properties. Oxley), to ensure that it is up-to-date and effective.
• Business owners are responsible for identifying
protected information to be backed up and D. Disaster Recovery
retention requirements. The disaster recovery plan must be maintained by
• Company information must be backed up on a Information Technology or its authorized service
regular basis to ensure recovery point and time provider to ensure the recovery or continuation of
objectives are met. the technology infrastructure critical to the Company
• Backups must be stored in a secured location following a natural or human-induced disaster.
accessible only to authorized users.
• The disaster recovery plan must be tested at least are not limited to, the following areas: Information
once annually and maintained by annual reviews, Security, Access Management, Change Management,
unless increased frequency is required in order to Configuration Management, Vulnerability
meet legal, regulatory, or compliance standards Management, and Physical Security.
applicable to the Company (e.g., PCI DSS, Sarbanes-
Oxley) to ensure that it is up-to-date and effective. B. Independent Third Party Assessments
Independent third parties, with the appropriate
expertise, must assess information security
CHANGE MANAGEMENT compliance on a periodic basis. Information Security &
Compliance is responsible for managing independent
Change management establishes mechanisms third party assessments.
to ensure the requirements of the Company
Information Security Program are met whenever C. Risk Assessments
technology infrastructure and application systems IT risk assessments that identify and evaluate threats
changes are installed into production. and vulnerabilities must be performed annually and
after a security incident, unless increased frequency
is required to meet legal, regulatory, or compliance
A. Infrastructure and Applications standards applicable to the Company (e.g., PCI DSS,
Information Technology or an authorized service Sarbanes-Oxley). Information Security & Compliance
provider is responsible for defining and maintaining a is responsible for managing risk assessments.
Change Management process.
• All technology infrastructure and application D. Vulnerability Scanning and Penetration Testing
systems used for production processing of critical Vulnerability scans and penetration tests must
business functions at the Company must employ a be performed, as required by legal, regulatory, or
formal change control process. compliance standards applicable to the Company
• The change control process must establish (e.g., PCI DSS, Sarbanes-Oxley). Information Security &
requirements for documentation of required Compliance is responsible for managing vulnerability
activities (e.g., testing), as well as authorizations and scanning and penetration testing.
approvals.
• Emergency changes to the Company production E. Vulnerability Management
environment must follow an emergency change Known vulnerabilities must be remediated, or
control procedure, including changes made to the Information Security & Compliance approved
Company production environment by third parties. compensating controls put in place, with timeliness
directly proportionate to the risk involved as required by
legal, regulatory, or compliance standards application to
COMPLIANCE the Company (e.g., PCI DSS, Sarbanes-Oxley).
C. Anti-Virus Protection
A. Inventory Information Technology or an authorized service
Information Technology or an authorized service provider is responsible for managing the anti-virus
provider is responsible for managing a device systems.
inventory. • Up-to-date anti-virus software must be installed
• The Company must maintain an inventory of on all Company or personal devices that store,
Company devices authorized for work use on the process, or transmit Company information and that
Company’s network. The inventory shall include are commonly affected by malicious software and
descriptive characteristics that enable the device to configured according to the Anti-Virus Standard.
be uniquely identified. Information Technology or an authorized service
• The Company must maintain lists of devices provider is responsible for implementing anti-virus
and related technologies, as well as associated software on devices.
authorization, location, and product lists as required • Anti-virus software log generation must be enabled
by specific compliance requirements (e.g., PCI DSS, and logs must be retained.
Sarbanes-Oxley). • Anti-virus software must not be disabled on any
• Inventory and security audits of company devices device without prior authorization from Information
must be performed at least once annually and Security & Compliance.
documented.
• Inventory of systems and applications that store
protected information must be maintained.
D. Configuration Standards
• All Company or personal devices that store ENCRYPTION
Company information must meet Company
Encryption management ensures protected
Configuration Standards as well as any laws,
Company information is not exposed to
regulations, and compliance standards applicable
unauthorized parties. Information Technology or
to the Company (e.g., PCI DSS, Sarbanes-Oxley).
an authorized service provider is responsible for
Information Technology is responsible for defining
encryption systems.
and maintaining Company configuration standards.
• Users must never disable or alter standard
configurations, security services, devices, or software. A. Encryption
• Company information must be encrypted according
E. Disposal to Company data classification.
• Company or personal devices that store Company • Information Technology is responsible for ensuring
information must be properly disposed of to ensure the appropriate encryption technology is applied
that no Company information remains on the device based on Company data classification.
(e.g., degaussing, physical destruction). See the • Only approved algorithms must be used as the basis
Equipment Disposal & Decommissioning Standard. for encryption technologies. See the Encryption
Standard for approved algorithms.
F. Inactivity
• Users must lock or logoff all devices whenever a
system is left unattended.
• Company and personal portable computing devices,
INCIDENT RESPONSE
desktops, and workstations must have a secure
Incident Response establishes the procedures that
inactivity timeout function enabled and set to 15
must be followed when responding to suspected
minutes or less.
or confirmed information security incidents.
Information Security & Compliance is responsible
G. Lost or Stolen
for managing the Incident Response Program.
• Users must immediately report any lost or stolen
devices, suspected or confirmed, to:
• Direct Supervisor or Manager; and A. Incident Reporting
• ISC@Hilton.com; and • All suspected, potential, and actual information
• HTS.Mobile@Hilton.com (mobile wireless security incidents must be reported immediately to
devices only). Information Security & Compliance at ISC@hilton.
• A standard tracking and recovery tool must be com. Information security incidents include, but are
installed on laptops. Information Technology or not limited to:
an authorized service provider is responsible for • Unauthorized access to electronic systems owned
installation. or operated by or for the Company;
• Users must never disable the standard tracking and • Malicious alteration or destruction of data,
recovery tool. information, or communications;
• Mobile phone and tablet configurations must allow • Unauthorized interception or monitoring of
remote wipes and disabling. communications; and
• Any deliberate and unauthorized destruction or
H. Vendor Management damage of IT resources.
• Vendors and service providers, who maintain • Information Security & Compliance must notify the
devices that store, process, or transmit Company appropriate entities according to the guidelines in
information must adhere to Sections A through G. the Incident Response Plan.
• Access logs must be maintained and protected • Wireless environments and technologies must
from unauthorized physical or logical access or be tested and deemed acceptable before being
modifications. installed and used.
• Audit trails must be consistently maintained and • Wireless networks must require authentication for
preserved for operating system events with security connectivity.
implications (e.g., security events). • Wireless network activity must be logged.
• Audit trail history must be retained for at least one • Scanning must be conducted twice per calendar
year, with a minimum of 90 days immediately year to identify unauthorized wireless access points,
available for analysis. unless more frequent scanning is required to meet
• Anti-Virus logs must be maintained for at least legal, regulatory, or compliance requirements
one year. applicable to the Company (e.g., PCI DSS, Sarbanes-
Oxley).
• An inventory identifying and describing all wireless
NETWORK technologies in use and the security measures in
place must be maintained.
Network management establishes requirements • Current network diagrams and cardholder data
to ensure the appropriate protection and flows must include wireless networks and must be
continuous operation of the Company network maintained.
infrastructure. Information Technology or its • Perimeter firewalls must be installed between
authorized service provider is responsible for any wireless networks and the cardholder data
managing the Company networks. environment. These firewalls must be configured
to deny or control (if such traffic is necessary for
A. Firewalls and General Network Security business purposes) any traffic from the wireless
• All Company private networks must be separated environment into the cardholder data environment.
from any non-Company private or public networks
by the use of a firewall device. C. Remote Access and Modem Security
• All inbound Internet connections to Company • Remote access to Company private networks must
private networks must be separated by the use of a be provisioned as defined in the Remote Access
firewall. Standard.
• The default firewall rule must deny all traffic except • Remote access over a public network such as
for explicitly approved traffic. the Internet or a wireless network must utilize
• All firewall and router rule sets must be reviewed at encryption technology (e.g. virtual private network)
least once every six months. as described in the Encryption Standard.
• All firewalls rules must restrict traffic based on • Modem connections inside Company facilities must
business requirements and meet legal, regulatory, be formally documented and approved.
or compliance standards applicable to the Company • Reviews must be conducted twice per calendar
(e.g., PCI DSS, Sarbanes-Oxley). year to identify unauthorized remote access
mechanisms, unless more frequent reviews are
B. Wireless required to meet legal, regulatory, or compliance
• Wireless access points must be architected, requirements applicable to the Company (e.g., PCI
installed, and maintained by the Company as DSS, Sarbanes-Oxley).
defined in the Wireless Standard. • Remote access used by vendors must be enabled
• Wireless access points cannot be placed on the only during the time period needed, monitored
Company network or installed in a Company facility when in use, and immediately deactivated when
without prior explicit written approval from access is no longer required.
#Standards-Architecture@hilton.com. • Remote access technologies must require an
• Wireless environments must conform to automatic session disconnect after a specific period
compliance standards applicable to the Company of inactivity.
(e.g., PCI DSS, Sarbanes-Oxley) as outlined in the
Wireless Standard.
VENDOR MANAGEMENT
A. Contract Language
• Vendor contracts must ensure the services
provided are consistently compliant with the
Company Information Security Policy and allow
for independent risk assessments to validate
compliance.
• Vendor contracts must require known
administrative, technical, and physical vulnerabilities
be remediated, or approved compensating controls
put in place, with timeliness directly proportionate
to the risk involved as required by legal, regulatory, or
compliance standards application to the Company
(e.g., PCI DSS, Sarbanes-Oxley).
• Vendor contracts must require documented
process and procedures be in place and followed
as required by legal, regulatory, or compliance
standards application to the Company (e.g., PCI DSS,
Sarbanes-Oxley).
• Vendor contracts must incorporate the Hilton
Privacy & Data Protection Policy for Service
Providers for third party vendors or resources that
store, process, or transmit protected information
as required by legal, regulatory, or compliance
standards application to the Company (e.g., PCI DSS,
Sarbanes-Oxley).
• Information Technology will lead and approve all
technology and technology enabled/enabling
agreements or contracts, including, but not
limited to, software, software-as-a-service, web
development, and hosting agreements.
B. Inventory
• A list of third party vendors or resources that store,
process, transmit, or access Company protected
information must be maintained by Information
Technology and available.
C. Monitoring
• A vendor management program, appropriate for the
vendor, must be defined and implemented to ensure
on-going compliance with key security and contract
requirements.
DEFINITIONS
TERM / ACRONYM DEFINITION
Awareness Training Training on the Information Security Policy for all new, existing, and
temporary team members with access to protected information.
Cardholder Data / Information Consists minimally of the full payment account number (PAN), but can also
include cardholder name, expiration date, and / or service code.
Company Those business entities that comprise Hilton, including Owned and Managed
properties, Franchise properties, and Corporate.
Company Information Information not intended for public consumption.
Company Information Assets The systems that store, process, or transmit Company information.
Company Data Classification Company Information groups that identify the proper handling of
information to ensure consistent protection when that information is stored,
processed, or transmitted. This policy references “protected information”,
which includes personally identifiable information (PII), financial information,
cardholder information, and health record information (HIPAA), as defined in
the Company’s Data Classification Policy.
Company Devices Company devices are pieces of hardware that are maintained or issued by
the Company that connect to the Company network or store Company
information (e.g. servers, desktop, laptop, smart phones, tablets, flash drives).
Generic User Account A user account used by more than one individual, thereby eliminating
accountability for actions taken with that account.
PCI DSS Payment Card Industry – Data Security Standards is an annual audit that
measures the safe handling of cardholder information at every step and is
conducted and validated by a Qualified Security Assessor (QSA).
Personal Devices Personal devices are any piece of hardware that is not issued by the
Company that connects to the Company network or stores Company
information, (e.g. smart phones, laptops, tablets, flash drives).
Portable Computing Devices Includes smart phones, tablets, and laptops.
Production Environment Technical environment where software and other products are put into
operation for their intended use by end users.
Protected Information See “Company Data Classification”.
Removable Computer Media Includes CDs and backup tapes.
Removable Storage Includes hard drives and USB flash drives and mobile phone drives.
Sarbanes-Oxley Sarbanes-Oxley Act of 2002 is a United States federal law that set new
or enhanced standards for all U.S. public company boards, management,
and public accounting firms to individually certify the accuracy of financial
information.
Security Controls Administrative, technical, and physical controls in place to protect Company
information assets (e.g., access management, encryption, firewalls, intrusion
detection and prevention, logging).
Security Tenets Confidentiality, Integrity, and Availability.
Shared User Account See “Generic User”.