ISMS Policies
Medivia Health Group’s ISMS Policies set out our core principles, objectives and commitments for protecting information security, data integrity and availability.
P00 OUR INFORMATION SECURITY POLICY
PURPOSE AND SCOPE
The purpose of this policy is to define the approach and objectives of senior management to prevent violations related to legal, regulatory, contractual obligations, and all kinds of security requirements, and to communicate these objectives to all employees and relevant parties.
The social, cultural, political, legal, regulatory, financial, technological, economic, natural, and competitive environment, whether international, national, regional, or local,
Key drivers and trends affecting the organization’s objectives,
Relations with external stakeholders and their perceptions and values.
RESPONSIBILITY:
The Information Security Management System (ISMS) Management Representative and the ISMS Team are responsible for preparing, reviewing, and updating the Information Security Policy. The management of Medivia Hospital/Medical Center approves and ensures the announcement of the Information Security Policy.
INFORMATION ASSETS:
Information assets are those owned by Medivia Hospital necessary to conduct its operations without disruption.
Information assets subject to this policy include:
All types of information and data presented in paper, electronic, visual, or audio media
All software and hardware used to access and modify information
Networks that enable information transfer
Departments, units, teams, and employees
Facilities and restricted areas
Solution partners
Services, products, or service providers supplied by third parties
POLICY:
Information resources such as information assets, facilities, and devices are of great importance to Medivia Hospital/Medical Center. Anyone using or providing information assets is responsible for protecting them.
All employees who use shared information assets are expected to act with necessary sensitivity, respecting colleagues, institutional employees, and corporate values.
Confidentiality is prioritized as a core institutional value; all personal information is protected by systems with the highest security standards. Information is not shared unless the owner consents, authorization is given, or legal requirements arise.
The most critical information assets and resources for Medivia Hospital/Medical Center are information assets, IT systems, IT equipment, and system rooms or data centers housing these assets, which must be carefully protected, kept confidential, and accessible when needed.
Information assets and resources may be located in different environments or locations. Regardless of their location or environment, customer communication requirements and corporate values determine their use.
Information security means not only ensuring confidentiality but also integrity and availability of information. Confidentiality means access to information assets is only given through proper authorization. Integrity means ensuring the completeness and accuracy of all information assets. Availability means information assets are accessible and usable when needed.
Due to the complexity and diversity of requirements related to the use, placement, and protection of information, comprehensive and extensive information security processes and policies must be defined. Accordingly, information security risks are evaluated by responsible persons, prioritized, and necessary measures are taken.
Ensuring the security of system rooms and data centers is a priority. Asset inventory and potential risks are identified in advance to guarantee uninterrupted and secure service to internal and external customers.
Decisions and actions prioritize reliable objective information and full use of technological capabilities. Actions are based not on intuition or appearances but on objective facts established by scientific and technological realities. For this reason, information is transferred and adopted from the world’s most advanced sources, and professional practices align accordingly. Resources are used efficiently, investments are made in technology, and development is pursued accordingly.
Therefore, it is recommended that the planning, implementation, monitoring, and improvement steps of the Information Security Management System be carried out in accordance with the TS ISO/IEC 27001 Information Security Management System standard and supporting standards.
POLICY LIST
P01 GENERAL USE POLICY FOR INFORMATION SYSTEMS
P02 INTERNET ACCESS POLICY
P03 EMAIL POLICY
P04 ANTIVIRUS POLICY
P05 PASSWORD POLICY
P06 PHYSICAL SECURITY POLICY
P07 SERVER SECURITY POLICY
P08 NETWORK MANAGEMENT POLICY
P09 DATABASE SECURITY POLICY
P10 CHANGE MANAGEMENT POLICY
P11 VIRTUAL PRIVATE NETWORK (VPN) POLICY
P12 IDENTITY AUTHENTICATION AND AUTHORIZATION POLICY
P13 ACCEPTABLE USE POLICY
P14 CLEAN DESK CLEAN SCREEN POLICY
P15 CRYPTOGRAPHIC CONTROLS POLICY
P16 VISITOR ACCEPTANCE POLICY
P17 MOBILE DEVICE POLICY
P18 THIRD-PARTY SECURITY POLICY
P19 INCIDENT BREACH REPORTING AND MANAGEMENT POLICY
P20 SECURE SOFTWARE DEVELOPMENT POLICY
P21 INFORMATION TECHNOLOGIES COMMUNICATION AND SPECIAL INTEREST GROUPS POLICY
P01 GENERAL INFORMATION SYSTEMS USAGE POLICY
1. Overview
The institution’s goal isn’t to impose restrictive policies but to foster a culture of transparency, trust, and integrity. It is committed to protecting both employees and the organization from illegal or harmful actions, whether intentional or not. Information systems are valuable assets. Strong security comes from teamwork involving everyone. All computer users must fully understand and take responsibility for these rules to perform their daily tasks.
2. Purpose
This policy aims to set a framework for the proper use of IT devices within the institution. Improper use can lead to virus attacks, network failures, service interruptions, and legal or disciplinary consequences.
3. Scope
Applies to all employees, contractors, and anyone working under the institution’s name. Also applies to all devices owned or leased by the institution.
4. Policy
General Use and Ownership
Users must understand that although reasonable privacy is provided, all data created within the institution belongs to the institution.
Installing unlicensed software on computers is strictly forbidden.
Critical information must be encrypted or stored securely, accessible only to authorized personnel.
Network settings, user definitions, and resource profiles on computers cannot be changed except by responsible IT or technical staff.
File exchanges outside of work-related files should be avoided.
Entertainment software, such as games, must not be run or copied.
Critical reports will be classified by sensitivity (e.g., Top Secret, Confidential, Company Internal, Public). The data owner is responsible for classification.
Users printing critical reports are responsible for protecting that information.
Anyone finding critical reports not belonging to them must report it to the hospital’s Information Security team.
“Confidential” paper documents must be stored in locked cabinets or safes.
Security and Personal Information
Access controls must be defined to prevent unauthorized access to critical information in systems.
Passwords must be kept secure, never shared, and changed every 90 days.
PCs and laptops must activate password-protected screensavers within 5 minutes of inactivity.
Laptops require extra protection; only essential data should be stored on them.
Lost or stolen laptops must be reported immediately.
Smartphones with institutional email must have password protection.
5. Prohibited Uses
Users must not use institutional resources for any illegal acts. Strictly forbidden activities include:
Unauthorized copying of intellectual property, trade secrets, patents, software licenses.
Copying books, digitizing magazine photos, or unauthorized software duplication.
Introducing malware into networks or servers.
Sharing account passwords or letting others use your account (including family when working remotely).
Using institutional computers for harassment or illegal activity.
Disrupting network communication.
Affecting user connections via scripts or commands.
Transmitting institutional information to third parties outside the institution.
Connecting personal devices to institutional computers without IT approval.
Installing or using software of unknown origin or not authorized by institution policies.
Email and Communication Activities
Accessing webmail from insecure external computers is prohibited.
Sending unsolicited emails, especially spam or unwanted ads, is forbidden.
Harassment via email or phone is prohibited.
Using institutional email accounts for personal use is not allowed.
P02 INTERNET ACCESS POLICY
Purpose
Define the standards required for secure internet access at Medivia. Improper internet use can cause legal liabilities, bandwidth abuse, and damage the institution’s reputation. This policy aims to prevent intentional or accidental misuse and ensure ethical and legal internet use.
Scope
Applies to all users of Medivia’s internet access.
Policy
Internet access will be controlled by content-filtering applications. Sites deemed inappropriate per institutional culture or law may be blocked.
Authorized users can use special services (FTP, Telnet, etc.) with manager approval.
Illegal websites must not be accessed, and unauthorized downloads are prohibited.
Third parties may use the internet only with IT approval and under defined rules.
Per law 5651, internet access logs are archived for at least 6 months.
Guest network access is separated by a dedicated wireless network isolated from the institutional network.
P03 EMAIL POLICY
Purpose
Set rules for the use of Medivia’s email infrastructure. Institutional emails are official identity carriers and vital communication channels, but their simplicity and speed also pose misuse risks.
Scope
Applies to all employees using institutional email.
Policy
3.1 Prohibited Use
Emails cannot be used for harassment, abuse, or violating recipient rights.
Care must be taken to ensure emails are only sent to intended recipients, safeguarding sensitive information.
Chain emails and emails with executable attachments must be deleted immediately and never forwarded.
Institutional emails must not be used to subscribe to personal mailing lists.
Do not respond to spam, chain, or phishing emails.
Emails requesting user credentials should be treated as phishing and deleted immediately.
Sending inappropriate content (pornography, racism, political propaganda, copyrighted material) is forbidden.
3.2 Personal Use
Personal use of email should be minimal and reasonable.
Users must protect messages from unauthorized access via passwords and security measures.
Emails must be regularly checked and sent using institutional identification.
Employees are responsible for preventing unauthorized access to institutional emails by outsiders.
Attachments from unknown sources must never be opened and should be deleted immediately.
Emails should be regularly archived off the main server to personal folders.
Any employment status changes must be promptly communicated to IT for account updates.
3.3 Monitoring
Employees must know their emails are not private and can be monitored by authorized personnel without prior notice.
3.4 Email Management
The institution is responsible for providing secure and reliable email services.
3.5 Email Virus Protection
Emails infected with viruses, worms, Trojans, or other malware must be scanned and cleaned by antivirus systems managed by IT.
P04 ANTIVIRUS POLICY
Purpose
To set the requirements ensuring all computers at Medivia/Institution/Medical Center/Hospital have effective virus detection and prevention standards.
Scope
Applies to all computers and servers at Medivia/Institution/Medical Center/Hospital.
Policy
All computers and servers must have antivirus software installed and kept up-to-date. Machines infected with viruses must be disconnected from the network until fully cleaned. Creating or spreading malware (worms, trojans, etc.) within the institution is strictly prohibited. No user is allowed to uninstall antivirus software for any reason.
Recommended actions against virus issues:
Antivirus updates run automatically on all computers.
Delete emails with attachments or macros from unknown senders, including from the recycle bin.
Delete spam emails.
Never download files from unknown or suspicious sources.
Removable media like CDs and USBs must be virus scanned before use.
P05 PASSWORD POLICY
Overview
Passwords are the first line of defense in computer security. Weak passwords can compromise the entire network. All staff and remote users must follow the rules below for password creation and maintenance.
Purpose
To establish standards for creating strong passwords, protecting them, and setting the frequency for changing them.
Scope
Applies to all users with accounts requiring passwords to access the computer network.
Policy
Passwords on all computers and servers must be changed every 90 days.
Users must be forced to change their initial passwords.
System administrators must use different passwords for each system.
Passwords must never be sent via email or included in any electronic form.
Users must be trained not to share passwords or write them down physically or electronically.
User accounts for both employees and external users must comply with institutional security policies.
User accounts must not be shared by multiple people.
P06 PHYSICAL SECURITY POLICY
Purpose
To prevent unauthorized access to the system room, work areas holding corporate information, and institutional buildings to protect personnel and critical institutional data.
Scope
Covers all physical security aspects related to access to information assets within institutional buildings.
Policy
Physical protection mechanisms must be established for the institution.
Different security zones should be defined based on the distribution and criticality of information, with controlled access rights and appropriate infrastructure.
Entry of external visitors and unauthorized personnel into secure areas must be supervised by authorized staff.
Access permissions to security zones must be regularly updated.
Critical systems must be housed in dedicated system rooms.
System rooms must be protected against power failures, voltage fluctuations, fire, and other disasters.
Cabinets and drawers must be locked and monitored.
Visitor and courier entries must be supervised by authorized personnel.
P07 SERVER SECURITY POLICY
1. Purpose
To define standards for basic security configurations of servers owned by the institution, minimizing unauthorized access to information and technology.
2. Scope
Applies to all servers owned by the institution.
3. Policy
3.1 Ownership and Responsibilities
Only authorized system administrators manage internal servers. Server installation and configuration is restricted to these authorized personnel.
All servers must be registered in the institution’s management system with details including:
Server name
Server function
Location
Hardware brand, model, serial number
Operating system
Installed application software
This information must be kept current in a centralized database.
General Configuration Rules
Unused services and applications must be disabled.
Servers must be hardened at the OS level.
External connections must comply with institutional rules.
Servers must be physically located in secure system rooms.
3.2 Operation
Servers must operate in environments with regulated power, network, temperature, and humidity.
Unauthorized access to system rooms must be prevented; access must be controlled and logged.
P08 NETWORK MANAGEMENT POLICY
Purpose
Ensure the security, confidentiality, integrity, and availability of the institution’s network and data. Special emphasis on remote access security and preventing unauthorized access. Controls must be applied to ensure network security and continuity.
Scope
System and network administrators and technical personnel managing the Medivia/Institution/Medical Center/Hospital network must operate according to this policy.
Policy
Controls must maintain network and connected systems’ business continuity.
Standards for allowed networks, services, and authorization methods must be defined.
User access to network services must be restricted.
Unlimited network roaming must be prevented.
Technical controls must actively monitor allowed communication between source and destination networks.
Network access should be segmented logically (e.g., VLANs) when needed.
Ports used for remote diagnostics and interventions must be secured.
Routing on the network must be controlled.
Configuration and setup of all network-connected computers must comply with institutional security policies.
Approved network interfaces and protocols must be used in system design and development.
Network addresses, configurations, and designs must be protected from third-party and unauthorized system access.
P09 DATABASE SECURITY POLICY
Purpose
Define standards to operate the institution’s database systems securely and without interruption.
Scope
All database systems fall under this policy.
Policy
Access to critical data is logged; no access to logs without authorized permission.
Data stored in databases must be classified, and appropriate backup policies established.
System administrators responsible for backups must ensure regular backups.
Backup procedures must be followed strictly.
Data storage systems must be kept in physically secure system rooms.
Maintenance, patches, and updates require prior notification to authorized personnel.
Data storage media cannot be removed from the institution without written approval from the Information Security Team Lead.
Only those with admin rights can directly access database servers (per Access and Usage Matrix).
Each authorized user must have a unique user ID with assigned permissions.
P10 CHANGE MANAGEMENT POLICY
Purpose:
Ensure changes to the institution’s information systems are made without compromising security or system continuity.
Scope:
All information systems and responsible personnel are covered.
Policy:
Only authorized personnel can make changes.
Before any change, identify all affected systems and notify relevant people.
Obtain approval from the responsible unit before implementing changes.
Prepare a detailed plan covering potential issues and rollback procedures, approved by management.
Define a testing process before the change.
Define timing and methods based on the criticality of the affected assets.
P11 REMOTE CONNECTION POLICY
Purpose:
Set standards for VPN use.
Scope:
Applies to all institutions, employees, contractors, consultants, temporary workers, and staff connecting to Medivia’s network via VPN.
Policy:
VPN must be used for remote access.
Authorized users have equal responsibilities whether on local or remote networks.
VPN users must prevent unauthorized access to their VPN rights.
All network traffic must pass through VPN and comply with security policies.
VPN gateways are managed by authorized personnel only.
Non-institutional devices must have up-to-date antivirus software installed.
Only approved users can use VPN.
Third parties must sign confidentiality agreements for VPN access.
P12 AUTHENTICATION AND AUTHORIZATION POLICY
Purpose:
Define policies for identity verification and authorization for system access.
Scope:
All internal and external users accessing Medivia systems.
Policy:
Define user identities and authentication methods per system.
Define profiles and authentication for external users.
Manage and audit roles and permissions across all software and systems centrally.
Keep access and authorization levels current.
Users are responsible for system security assigned to them.
Access logs must be regularly maintained.
Users must keep passwords confidential.
Monitor and record privilege escalations or misuse.
No shared accounts; every user gets a unique account.
P13 ACCEPTABLE USE POLICY
Purpose:
Define business rules employees and contractors must follow to maintain confidentiality, integrity, and availability of systems and data.
Scope:
All staff and contractors who interact with critical information assets.
Policy:
All must comply with security policies in their scope.
HR and management communicate policies to all employees and contractors; adherence is mandatory and contractually enforced.
All information stored or transmitted in the environment belongs to the institution and can be monitored.
Confidential information must not be copied or shared outside business needs.
Users must protect access credentials and device security; sharing access info is forbidden.
Antivirus software must never be disabled.
Unauthorized copying of licensed software is prohibited.
No scanning, monitoring, or listening to the institutional IT network without permission.
No user may exceed their assigned computer permissions.
Enforcement:
Disciplinary action per company procedures for violations.
P14 CLEAN DESK AND SCREEN POLICY
Purpose:
Prevent risks from unauthorized access or misuse of sensitive information during and outside work hours.
Scope:
Desks, screens, printed documents, records.
Responsibility:
All employees must comply.
Implementation:
Confidential documents and data must be securely stored (lockers, safes) after use.
Dispose of obsolete sensitive info via shredding, burning, or secure destruction.
No documents left on phones, fax, or copiers.
Screens and devices must be password-protected; screen savers with passwords activated after 5-10 minutes inactivity.
Computers must be locked or turned off outside working hours and when unattended during working hours.
Printers must not retain classified printouts unattended.
Desktop folders/files must be organized.
Passwords must never be written on paper or left exposed.
Sensitive data must be stored with cryptographic encryption.
High-risk data requires strong encryption.
Mobile device data must be protected with strong passwords.
Smartphones with email must have lock enabled.
Passwords must be changed regularly.
P16 VISITOR ACCEPTANCE POLICY
Purpose:
Define rules for admitting, monitoring, and escorting external visitors.
Responsibility:
All managers and employees.
Implementation:
Reception greets and directs visitors.
Visitors must be met at entry by their host.
Visitors can only access meeting rooms; access to work areas is forbidden except maintenance/inspection staff.
Couriers and delivery people wait at reception.
Visitor information is recorded.
Visitors cannot use the institution’s internet.
Enforcement:
Disciplinary actions apply for non-compliance.
P17 MOBILE AND PORTABLE DEVICE POLICY
Purpose:
Set rules for the use of mobile and portable devices containing institutional information.
Responsibility:
All employees.
Implementation:
Devices with institutional data are assigned with a formal record.
Employees are responsible for device security and proper use.
Portable computers are given with restricted admin rights.
No external software or content promoting politics, racism, violence, pornography, or erotica is allowed on devices.
No illegal or damaging communication via institution phones/computers.
Antivirus must never be disabled.
Work done on portable devices must be saved on the network.
Mobile devices must be carefully controlled due to risk of loss/theft.
Enforcement:
Disciplinary action applies for violations.
P18 THIRD-PARTY SECURITY POLICY
Purpose:
Ensure security when third parties access Medivia’s information systems.
Responsible:
IT, HR, and Administrative Affairs.
Application:
Third-party maintenance, repair staff, and suppliers must sign confidentiality agreements or contracts before entering and while inside the institution.
Access to systems is limited to authorized scopes.
VPN policy applies for third-party computers allowed to access the network.
Medivia can cut off third-party access at any time without notice.
Access agreements with conditions must be signed before third-party access.
Enforcement:
Disciplinary procedures for violations.
P19 INCIDENT VIOLATION REPORTING AND MANAGEMENT POLICY
Purpose:
Define processes for handling information security incidents and violations.
Responsible:
All personnel.
Application:
All breaches affecting confidentiality, integrity, availability, unauthorized access, or data tampering must be recorded.
A feedback process must be in place to report, handle, and close incidents.
Incident forms must be filled with the InfoSec team.
Identify violators and assess if the incident is criminal.
Employees, third parties, and contractors must report security weaknesses ASAP to management or InfoSec.
Incident response includes root cause analysis, prevention, corrective actions, communication with affected parties, and reporting to authorities.
Evidence collection must ensure admissibility, completeness, and integrity for potential legal use.
Measures to fix vulnerabilities and prevent recurrence must be implemented.
Lessons learned must inform new controls to avoid repeat incidents.
Enforcement:
Disciplinary procedures for violations.
P20 SECURE SOFTWARE DEVELOPMENT POLICY
Management must ensure only appropriate software projects start and infrastructure is suitable.
Decide clearly whether software is developed internally or purchased.
Use a proper plan covering requirements, feasibility, design, development, testing, and approval.
Internal or packaged software must meet needs.
Software not compliant with national/international standards or without institutional request must not be integrated.
All new/revised software must be tested and approved.
Deployment must be controlled.
Software must be classified, tagged, inventoried, and updated in asset records.
Internal development must follow published development standards (naming, comments, language, etc.).
Personal, unauthorized software development is prohibited.
Data migration from old systems must be complete, accurate, and unauthorized changes prevented.
P21 IT COMMUNICATION AND SPECIAL INTEREST GROUPS POLICY
Contact info for IT, HBYS (Hospital Management System), servers, infrastructure (UPS, generators), external services (Pronet), authorities (fire, police, ambulance), and admin services must be used when needed.
INFORMATION SECURITY POLICY APPROVAL FORM
Confirms the reader has read, understood, and accepted Medivia’s Information Security Policy.
To be signed by IT staff, managers, and top management responsible for policy enforcement.
Procedure: read the policy, date and sign specified sections, submit to relevant manager.
