Presented at The New Generation IT Doctor for Hospital Development Training Program, Thai Medical Informatics Association, Nonthaburi, Thailand on August 26, 2019
āļĢāļ°āļāļāļāļēāļĢāļāļąāļāļāļēāļĢāļāđāļāļĄāļđāļĨāļāļ§āļēāļĄāļĨāļąāļāļāļđāđāļāđāļ§āļĒ (Thailand LA Forum 2017 āļŠāļ āļēāđāļāļāļāļīāļāļāļēāļĢāđāļāļāļĒāđ) ...Nawanan Theera-Ampornpunt
āļĢāļ°āļāļāļāļēāļĢāļāļąāļāļāļēāļĢāļāđāļāļĄāļđāļĨāļāļ§āļēāļĄāļĨāļąāļāļāļđāđāļāđāļ§āļĒ (Thailand LA Forum 2017 āļŠāļ āļēāđāļāļāļāļīāļāļāļēāļĢāđāļāļāļĒāđ) ...Nawanan Theera-Ampornpunt
2. 2003 M.D. (First-Class Honors) (Ramathibodi)
2009 M.S. in Health Informatics (U of MN)
2011 Ph.D. in Health Informatics (U of MN)
âĒ Faculty of Medicine Ramathibodi Hospital
Mahidol University
o Assistant Dean for Informatics
o Lecturer, Section for Clinical Epidemiology &
Biostatistics
âĒ Member, TMI Executive Board
nawanan.the@mahidol.ac.th
SlideShare.net/Nawanan
Facebook.com/NawananT
Line ID: NawananT
Introduction
4. âĒ TMI HITQIF Framework
âĒ IT Governance
âĒ Strategic Planning & IT Master Plan
âĒ Structure, Roles, Team Development &
Roadmap to IT Quality
âĒ IT Policy, Regulation, Risk & Security
Management
âĒ Service Level Management, IT Service Desk &
Data Center Management
âĒ Data Management
âĒ IT Process, Metrics & Control
âĒ Continuous & Sustainable IT Quality
Improvement
Overall Topics of HITQIF Course
17. Sources of the Threats
⊠Hackers
⊠Viruses & Malware
⊠Poorly-designed systems
⊠Insiders (Employees)
⊠Peopleâs ignorance & lack of knowledge
⊠Disasters & other incidents affecting information
systems
18. ⊠Information risks
⊠Unauthorized access & disclosure of confidential information
⊠Unauthorized addition, deletion, or modification of information
⊠Operational risks
⊠System not functional (Denial of Service - DoS)
⊠System wrongly operated
⊠Personal risks
⊠Identity thefts
⊠Financial losses
⊠Disclosure of information that may affect employment or other
personal aspects (e.g. health information)
⊠Physical/psychological harms
⊠Organizational risks
⊠Financial losses
⊠Damage to reputation & trust
⊠Etc.
Consequences of Security Attacks
19. ⊠Privacy: âThe ability of an individual or group to
seclude themselves or information about
themselves and thereby reveal themselves
selectively.â (Wikipedia)
⊠Security: âThe degree of protection to safeguard
... person against danger, damage, loss, and
crime.â (Wikipedia)
⊠Information Security: âProtecting information
and information systems from unauthorized
access, use, disclosure, disruption,
modification, perusal, inspection, recording or
destructionâ (Wikipedia)
Privacy & Security
22. Examples of Integrity Risks
http://www.wired.com/threatlevel/2010/03/source-code-hacks/
http://en.wikipedia.org/wiki/Operation_Aurora
âOperation Auroraâ
Alleged Targets: Google, Adobe, Juniper Networks,
Yahoo!, Symantec, Northrop Grumman, Morgan Stanley,
Dow Chemical
Goal: To gain access to and potentially modify source
code repositories at high tech, security & defense
contractor companies
23. Examples of Integrity Risks
http://news.softpedia.com/news/700-000-InMotion-Websites-Hacked-by-TiGER-M-TE-223607.shtml
Web Defacements
24. Examples of Availability Risks
http://en.wikipedia.org/wiki/Blaster_worm
Viruses/worms that led to instability &
system restart (e.g. Blaster worm)
25. Examples of Availability Risks
http://en.wikipedia.org/wiki/Ariane_5_Flight_501
Ariane 5 Flight 501 Rocket Launch Failure
Cause: Software bug on rocket acceleration due to data conversion
from a 64-bit floating point number to a 16-bit signed integer without
proper checks, leading to arithmatic overflow
31. āļŦāļĨāļąāļāļāļĢāļīāļĒāļāļĢāļĢāļĄāļāļĩāđāđāļāļĩāđāļĒāļ§āļāļąāļ Privacy
âĒ Autonomy (āļŦāļĨāļąāļāđāļāļāļŠāļīāļāļāļīāđ/āļāļ§āļēāļĄāđāļāđāļāļāļīāļŠāļĢāļ°āļāļāļāļāļđāđāļāđāļ§āļĒ)
âĒ Beneficence (āļŦāļĨāļąāļāļāļēāļĢāļĢāļąāļāļĐāļēāļāļĢāļ°āđāļĒāļāļāđāļŠāļđāļāļŠāļļāļāļāļāļāļāļđāđāļāđāļ§āļĒ)
âĒ Non-maleficence (āļŦāļĨāļąāļāļāļēāļĢāđāļĄāđāļāļēāļāļąāļāļāļĢāļēāļĒāļāđāļāļāļđāđāļāđāļ§āļĒ)
âFirst, Do No Harm.â
32. Hippocratic Oath
...
What I may see or hear in the course of
treatment or even outside of the treatment
in regard to the life of men, which on no
account one must spread abroad, I will
keep myself holding such things shameful
to be spoken about.
...
http://en.wikipedia.org/wiki/Hippocratic_Oath
38. ⊠Attack
⊠An attempt to breach system security
⊠Threat
⊠A scenario that can harm a system
⊠Vulnerability
⊠The âholeâ that is used in the attack
Common Security Terms
39. ⊠Identify some possible means an
attacker could use to conduct a
security attack
Class Exercise
41. Alice
Simplified Attack Scenarios
Server Bob
- Physical access to client computer
- Electronic access (password)
- Tricking user into doing something
(malware, phishing & social
engineering)
Eve/Mallory
42. Alice
Simplified Attack Scenarios
Server Bob
- Intercepting (eavesdropping or
âsniffingâ) data in transit
- Modifying data (âMan-in-the-middleâ
attacks)
- âReplayâ attacks
Eve/Mallory
43. Alice
Simplified Attack Scenarios
Server Bob
- Unauthorized access to servers through
- Physical means
- User accounts & privileges
- Attacks through software vulnerabilities
- Attacks using protocol weaknesses
- DoS / DDoS attacks Eve/Mallory
45. Alice
Safeguarding Against Attacks
Server Bob
Administrative Security
- Security & privacy policy
- Governance of security risk management & response
- Uniform enforcement of policy & monitoring
- Disaster recovery planning (DRP) & Business continuity
planning/management (BCP/BCM)
- Legal obligations, requirements & disclaimers
46. Alice
Safeguarding Against Attacks
Server Bob
Physical Security
- Protecting physical access of clients & servers
- Locks & chains, locked rooms, security cameras
- Mobile device security
- Secure storage & secure disposition of storage devices
47. Alice
Safeguarding Against Attacks
Server Bob
User Security
- User account management
- Strong p/w policy (length, complexity, expiry, no meaning)
- Principle of Least Privilege
- âClear desk, clear screen policyâ
- Audit trails
- Education, awareness building & policy enforcement
- Alerts & education about phishing & social engineering
48. Alice
Safeguarding Against Attacks
Server Bob
System Security
- Antivirus, antispyware, personal firewall, intrusion
detection/prevention system (IDS/IPS), log files, monitoring
- Updates, patches, fixes of operating system vulnerabilities &
application vulnerabilities
- Redundancy (avoid âSingle Point of Failureâ)
- Honeypots
49. Alice
Safeguarding Against Attacks
Server Bob
Software Security
- Software (clients & servers) that is secure by design
- Software testing against failures, bugs, invalid inputs,
performance issues & attacks
- Updates to patch vulnerabilities
50. Alice
Safeguarding Against Attacks
Server Bob
Network Security
- Access control (physical & electronic) to network devices
- Use of secure network protocols if possible
- Data encryption during transit if possible
- Bandwidth monitoring & control
51. Alice
Safeguarding Against Attacks
Server Bob
Database Security
- Access control to databases & storage devices
- Encryption of data stored in databases if necessary
- Secure destruction of data after use
- Access control to queries/reports
- Security features of database management systems (DBMS)
54. ⊠Access control
⊠Selective restriction of access to the system
⊠Role-based access control
⊠Access control based on the personâs role
(rather than identity)
⊠Audit trails
⊠Logs/records that provide evidence of
sequence of activities
User Security
55. ⊠Identification
⊠Identifying who you are
⊠Usually done by user IDs or some other unique codes
⊠Authentication
⊠Confirming that you truly are who you identify
⊠Usually done by keys, PIN, passwords or biometrics
⊠Authorization
⊠Specifying/verifying how much you have access
⊠Determined based on system ownerâs policy & system
configurations
⊠âPrinciple of Least Privilegeâ
User Security
56. ⊠Nonrepudiation
⊠Proving integrity, origin, & performer of an
activity without the personâs ability to refute
his actions
⊠Most common form: signatures
⊠Electronic signatures offer varying degrees of
nonrepudiation
⊠PIN/password vs. biometrics
⊠Digital certificates (in public key infrastructure
- PKI) often used to ascertain nonrepudiation
User Security
57. ⊠Multiple-Factor Authentication
⊠Two-Factor Authentication
⊠Use of multiple means (âfactorsâ) for authentication
⊠Types of Authentication Factors
⊠Something you know
⊠Password, PIN, etc.
⊠Something you have
⊠Keys, cards, tokens, devices (e.g. mobile phones)
⊠Something you are
⊠Biometrics
User Security
58. Need for Strong Password Policy
So, two informaticians
walk into a bar...
The bouncer says,
"What's the password."
One says, "Password?"
The bouncer lets them
in.
Credits: @RossMartin & AMIA (2012)
59. Unknown Internet sources, via
http://pikabu.ru/story/interesno_kakoy_zhe_u_nikh_parol_4274737,
via Facebook page âāļŠāļāļāđāļŪāļāđāļ§āđāļāđāļāļāđāļĄāļ§āđâ
Whatâs the Password?
61. Recommended Password Policy
⊠Length
⊠8 characters or more (to slow down brute-force attacks)
⊠Complexity (to slow down brute-force attacks)
⊠Consists of 3 of 4 categories of characters
⊠Uppercase letters
⊠Lowercase letters
⊠Numbers
⊠Symbols (except symbols that have special uses by the
system or that can be used to hack system, e.g. SQL
Injection)
⊠No meaning (âDictionary Attacksâ)
⊠Not simple patterns (12345678, 11111111) (to slow down brute-
force attacks & prevent dictionary attacks)
⊠Not easy to guess (birthday, family names, etc.) (to prevent
unknown & known persons from guessing)Personal opinion. No legal responsibility assumed.
62. Recommended Password Policy
⊠Expiration (to make brute-force attacks not possible)
⊠6-8 months
⊠Decreasing over time because of increasing computerâs
speed
⊠But be careful! Too short duration will force users to write
passwords down
⊠Secure password storage in database or system
(encrypted or store only password hashes)
⊠Secure password confirmation
⊠Secure âforget passwordâ policy
⊠Different password for each account. Create variations
to help remember. If not possible, have different sets of
accounts for differing security needs (e.g., bank
accounts vs. social media sites) Personal opinion. No legal responsibility assumed.
63. Techniques to Remember Passwords
⊠http://www.wikihow.com/Create-a-Password-You-Can-
Remember
⊠Note that some of the techniques are less secure!
⊠One easy & secure way: password mnemonic
⊠Think of a full sentence that you can remember
⊠Ideally the sentence should have 8 or more words, with
numbers and symbols
⊠Use first character of each word as password
⊠Sentence: I love reading all 7 Harry Potter books!
⊠Password: Ilra7HPb!
⊠Voila!
Personal opinion. No legal responsibility assumed.
64. Dear mail.mahidol.ac.th Email Account User,
We wrote to you on 11th January 2010 advising that you change the password on
your account in order to prevent any unauthorised account access following
the network instruction we previously communicated.
all Mailhub systems will undergo regularly scheduled maintenance. Access
to your e-mail via the Webmail client will be unavailable for some time
during this maintenance period. We are currently upgrading our data base
and e-mail account center i.e homepage view. We shall be deleting old
[https://mail.mahidol.ac.th/l accounts which are no longer active to create
more space for new accountsusers. we have also investigated a system wide
security audit to improve and enhance
our current security.
In order to continue using our services you are require to update and
re-comfirmed your email account details as requested below. To complete
your account re-comfirmation,you must reply to this email immediately and
enter your account
details as requested below.
Username :
Password :
Date of Birth:
Future Password :
Social Engineering Examples
Real social-engineering e-mail received by Speaker
66. ⊠Poor grammar
⊠Lots of typos
⊠Trying very hard to convince you to open
attachment, click on link, or reply without
enough detail
⊠May appear to be from known person (rely on
trust & innocence)
Signs of a Phishing Attack
67. ⊠Donât be too trusting of people
⊠Always be suspicious & alert
⊠An e-mail with your friendâs name & info doesnât have to
come from him/her
⊠Look for signs of phishing attacks
⊠Donât open attachments unless you expect them
⊠Scan for viruses before opening attachments
⊠Donât click links in e-mail. Directly type in browser using
known & trusted URLs
⊠Especially cautioned if ask for passwords, bank
accounts, credit card numbers, social security numbers,
etc.
Ways to Protect against Phishing
70. ⊠Virus
⊠Propagating malware that requires user action
to propagate
⊠Infects executable files, data files with
executable contents (e.g. Macro), boot
sectors
⊠Worm
⊠Self-propagating malware
⊠Trojan
⊠A legitimate program with additional, hidden
functionality
Malware
71. ⊠Spyware
⊠Trojan that spies for & steals personal
information
⊠Logic Bomb/Time Bomb
⊠Malware that triggers under certain conditions
⊠Backdoor/Trapdoor
⊠A hole left behind by malware for future
access
Malware
72. ⊠Rogue Antispyware
⊠Software that tricks or forces users to pay before
fixing (real or hoax) spyware detected
⊠Rootkit
⊠A stealth program designed to hide existence of
certain processes or programs from detection
⊠Botnet
⊠A collection of Internet-connected computers that
have been compromised (bots) which controller of the
botnet can use to do something (e.g. do DDoS
attacks)
Malware
87. ⊠Installed & updated antivirus, antispyware, &
personal firewall
⊠Check for known signatures
⊠Check for improper file changes (integrity failures)
⊠Check for generic patterns of malware (for unknown
malware): âHeuristics scanâ
⊠Firewall: Block certain network traffic in and out
⊠Sandboxing
⊠Network monitoring & containment
⊠User education
⊠Software patches, more secure protocols
Defense Against Malware
88. ⊠Social media spams/scams/clickjacking
⊠Social media privacy issues
⊠User privacy settings
⊠Location services
⊠Mobile device malware & other privacy risks
⊠Stuxnet (advanced malware targeting certain
countries)
⊠Advanced persistent threats (APT) by
governments & corporations against specific
targets
Newer Threats
89. ⊠Most common reason for security bugs is
invalid programming assumptions that attackers
will look for
⊠Weak input checking
⊠Buffer overflow
⊠Integer overflow
⊠Race condition (Time of Check / Time of Use
vulnerabilities)
⊠Running programs in new environments
Software Security
Adapted from Nicholas Hopperâs teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
90. ⊠Defense in Depth
⊠Multiple layers of security defense are
placed throughout a system to provide
redundancy in the event a security
control fails
⊠Secure the weakest link
⊠Promote privacy
⊠Trust no one
Secure Software Design Principles
Saltzer & Schroeder (1975), Viega & McGraw (2000)
Adapted from Nicholas Hopperâs teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
http://en.wikipedia.org/wiki/Defense_in_depth_(computing)
91. ⊠Modular design
⊠Check error conditions on return values
⊠Validate inputs (whitelist vs. blacklist)
⊠Avoid infinite loops, memory leaks
⊠Check for integer overflows
⊠Language/library choices
⊠Development processes
Secure Software Best Practices
Adapted from Nicholas Hopperâs teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
108. âĒ āđāļāđāļāđāļāđāļ 11 āļŦāļĄāļ§āļ (Domains)
â Security policy
â Organization of information security
â Asset management
â Human resources security
â Physical and environmental security
â Communications and operations management
â Access control
â Information systems acquisition, development and
maintenance
â Information security incident management
â Business continuity management
â Regulatory compliance
āļĄāļēāļāļĢāļāļēāļ Security āļāļēāļĄāļ§āļīāļāļĩāļāļēāļĢāđāļāļāļāļĨāļāļāļ āļąāļĒ
115. âPolicy & Guidelines/Work Instructions on
o Data completeness & integrity
o System security
o Patient information privacy & confidentiality
protections
o Secure data storage, retention & destruction
o Monitoring, evaluation & enforcement
âCommunication of Policy & Guidelines
IT Security & Privacy Policy Checklist
117. ⊠Project failures
⊠Waste investments
⊠Security breaches
⊠System crashes
⊠Failures by service providers to understand and
meet customer requirements
⊠System errors or bugs
Examples of IT Risks
118. Risk Strategies
âĒ Accept/ignore
âĒ Avoid completely
âĒ Reduce risk
likelihood or
impact
âĒ Transfer risk to
someone else (e.g.
insurance)
Marchewka (2006)
Risk = f(likelihood x impact)
Risk Management