Project21.txt
The proposal is a one page single space plan for your project and a separate five source annotated reference list. The annotations include two paragraphs for each source. One paragraph is a summary of the source and the second paragraph is your reflection
Your final project is a 12 minute presentation to be presented at residency. You must select a topic from the list provided in this weeks folder. Each presentation must be unique. The final project must include 20 slides, a one page single spaced abstract, and a reference list. The proposal is a one page single space plan for your project and a separate five source annotated reference list. The annotations include two paragraphs for each source. One paragraph is a summary of the source and the second paragraph is your reflection (Iwhat you thought about it as a source). The proposal is due by (03/16) – not the full presentation.
Topics:
Database security compliance with anti-money laundering statutes
Risks of overly privileged users
Auditing v. monitoring
Maintaining data integrity with hash functions
Security risks in database migration
Quantitative risk assessment methodologies
Qualitative risk assessment methodologies
Reducing costs with tiered storage
Physical protections for your database
IOT threats to database security
TDE
Tokenization
Global data Integrity violation examples
Efficient disaster recovery
How to effect litigation holds
Data as evidence: what is chain of custody?
Data as evidence: The Federal Rules of Civil Procedure
GDPR Compliance
HIPAA Compliance
SOX Compliance
Database STIGs
ISO Database Security Framework
NIST Database Security Framework
Patch management and the medical device
Strict Liability v. Ordinary Negligence for the DBA
How Oracle 12c advances the security discussion
How Stuxnet exposed the exceptional importance of data integrity
Are Data integrity violations worse than confidentiality breaches?
How the tsunami of data expansion increases security concerns
Mobile users and data security
Why is vulnerability assessment critical for data security?
Legitimate privilege abuse ad how to prevent it
Monitoring your most highly privileged users – what the regulations say.
Creating a database security culture
Vulnerable storage media?
Patching – To automate or not?
What do you have – inventorying your legacy data.
The human factor – how to keep your DBA up-to-date
Monitoring database use patterns to detect anomalies
Quantitative v. Qualitative security risk assessment