Database Forensics
Database Forensics
Forensics
Denys A. Flores
20 Jan
2016
Data Breaches
► They happen around the world and
sometimes security officers are not aware of
them after a few week s/ m ont h s
0
Protocol- level vulnerabilities (SSL Heartbleed)
° Kernel Vulnerabilities (bypass ASLR and DEP)
0
Application Bugs (heap / st ack over fl ows /
legacy code)
0
Third- party plug- ins
0
Web - based attacks (SQL injection / Do s)
Outsiders (external threats)
0
Malware (Troj ans/ RAT s / Rogue ware)
Insiders (internal threats)
► The major source of costly
data breaches
0
IP Spoofing
0
Sn i f f i ng / Scanning
° Credential Misuse
0
Unauthorised Information Disclosure (Negligence
Insiders (internal threats)
or Intentional)
Security Management
Issues
► Weak information security policy
► Security Architecture
0
Incident management technologies do not consider data
management and classification
° Companies think that security tools are the silver bullet for all
security problems
0
Device misconfiguration
► Cloud Services
0
Effective outsourced security management
0
Effective outsourced data/ information management
0
Effective physical / logical access control to database servers
Security and
Forensics
► As a database stores information, information
security principles apply.
► Information Security:
0
A set of human and technical measures and procedures to
protect information security properties:
• Confidentiality
• Integrity
• Availability
• Possession or Control
• Authenticity
• Authentication
• Non-repudiation
• Provenance
• Authorization
• Utility
· Accountability
Security and
Forensics
► Accountability
0
Security characteristic to track activities of identification,
authorization and access to ensure that an actor with
access to resources behaves in accordance with security,
business and ethics rules (non- repud i atio n)
0
It considers the fact that a fully secure system does not
exist, so in case of a security event (e.g. data breach), this
must be associated to the attacker by using accurate and
reliable digital evidence (provenance)
0
Requires proper monitoring and logging of actions to
ensure the proper storage, use and maintenance of
databases
0
It is related to auditing and forensics purposes
Security and
Forensics
► Auditing
0
Methodological and recurring examination and
review of activities over a period of ti me.
0
Ensures compliance with laws, policies and other
regulations by using accurate records of who did
what and when.
0
Relies on authentication and authorisation controls.
Security and
Forensics
► Forensics
0
Methodological identification, preservation,
acquisition and examination of digital evidence to
report and reflect on a security event that may have
legal implications.
0
Is a vital process for incident response to
analyse an event in a timely manner, and if
possible, identify the parties involved.
0
Relies on evidence provenance.
Database Forensics
► The main research focus in database security
has been extern al threats (outsiders)
0
Reactive Approach
0
Proactive Approach
Database Forensics
► Reactive Approach:
0
After a security event (e.g. data breach) has occurred
0
Reconstruct or recover an original state of the database
0
Rely on traditional digital forensics analysis (imaging
and data carving) which are not fully compatible with
the complexity of databases, and may not ensure
evidence integrity and its admissibility in legal
proceedings
0
Not effective for incident response (limited time and
resources)
0
Ad- hoc practices depending on the DBMS (MSSQL / Or acle)
Database Forensics
► Proactive Approach
0
Resilience / Readiness:
0
If evidence integrity is ensured then evidence is
admissible because the systems that generated it are
reliable (trustworthiness)
0 Audit requirements
• Generate reliable evidence by logging and monitoring user action on the
database
+
° Forensics requirements
• Investigate incidents by identifying, preserving, acquiring and
evaluating / analyzing evidence to finally report and reflect on the events
Conclusions
► Database misuse / fraud
is mostly performed by insiders, however in
the field of database
forensics, this problem has drawn very little
attention
► Reactive approachesfor
database forensics are
more developed, but not fully admissible for
forensic purposes
► A proactive database
forensics architecture should be
considered to gather evidence from
different sources (network, servers, database)
Conclusions
► This architecture must
consider aspects of both, forensics and
auditing activities to ensure evidence
integrity