0% found this document useful (0 votes)
13 views7 pages

Database Security Vulnerabilities and Solutions

1) The document describes various threats, vulnerabilities, assets, existing controls, likelihood and consequences of risks related to an organization's systems and databases. Key risks discussed include corruption of files, altering of account records, and theft of personal information from the database. Most risks were found to be high or medium level. 2) Suitable security policies are proposed to prevent the discussed attacks, such as implementing proper authentication mechanisms, restricting privileges, using strong encryption, and multifactor authentication. 3) The Griffith policy is analyzed, noting it should more clearly specify authentication methods and access controls to avoid confusion.

Uploaded by

akshaynew2011
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views7 pages

Database Security Vulnerabilities and Solutions

1) The document describes various threats, vulnerabilities, assets, existing controls, likelihood and consequences of risks related to an organization's systems and databases. Key risks discussed include corruption of files, altering of account records, and theft of personal information from the database. Most risks were found to be high or medium level. 2) Suitable security policies are proposed to prevent the discussed attacks, such as implementing proper authentication mechanisms, restricting privileges, using strong encryption, and multifactor authentication. 3) The Griffith policy is analyzed, noting it should more clearly specify authentication methods and access controls to avoid confusion.

Uploaded by

akshaynew2011
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

A)

1)

Threat/ Asset Existing Likelihood Consequence Level


Vulnerability Controls of
Risk

Corruptionof Integrityof ACLwithout Duetono Financialdata High


Filesby Customer proper authentication thatiscrucial
altering authentication mechanism forthe
records mechanism exploitingis organsiation
madesimple
here
Alteringof IntegrityofPoorPassword SQLisanold Alteringrecords High
account case Management conceptandnot wouldlead
records investigatio policies muchskillsis organization
nonsame without neededto wronginsights
recordson biometricsto exploitusing intogrowthof
theserver allowproper thistechnique organisation
login
Theftof Copyof Database SQLisanold Theattacker Mediu
personal information without conceptandnot mayusethisto m
information from recommended muchskillsis takearansom
andusingit Database Securitylevel neededto from
forpersonal mechanisms exploitusing organisationand
use this sellthedataof
[Link] organisation
ivenessofXSS
dependson
programming
knowledgeof
person
executingattack
Please note below is an extra information apart from above information that can also be added if
you wish

Threat/Vulnerab Levelof Conseque Likehood Asset ExistingControls


ility Risk nce
Broken Severe Secure Duetono Host Poor
Authentication and authentication System Authentication
Easyloginusing Important mechanism mechanism
anyrandom Informati exploitingis
usernameand onwould madesimple
password belost here
SQL Severe Any SQLisanold Databas PoorDatabase
Injection:Extract informati conceptand e securitypolicy
ionofvarious onlike notmuch without
dataontargetby financial skillsis encryption
queryexecution infocan neededto
be exploitusing
comprom thistechnique
ised
CROSSSITE Moderate Usermay Noteasyor Databas UsageofSpecial
SCRIPTING:Inv be notvery eand charactersallowed
olvesrunning trickedto [Link] Host inusernamefield
randomscripts givehis ndson System
intarget informati programming
machine on skillsof
person
ImproperACL Low Access Exploitationis Host Samepriveledges
Configuration maybe veryunlikely System toallusers
granted butpossibility
toany cantbe
random completely
user ruledout
2)Some Suitable Security Policies that can be in place to prevent the attacks include

i)ProperAuthenticationmechanismshouldbeimplementedwhereeverpossible

ii)Itsrecommendedtoclearhistory,cookies,cacheandrestrictpriveledgestopeople

iii)[Link]
input

iv)Modifypriveledgestoselectedusers

v)Asanadditionallevelofsecuritybiometricsecuritycanbeusedtoallowaccesstoemployees
oftheorganization

vi)Proper DatabaseSecurityPolicies withstrongencryption mechanism(employing256AES


encryptionmechanisms)shouldbeusedtoavoidexploitationofdata
vii)If required the Organisation can implement a mechanism where if un authorized people
accessthedatabase,[Link]
disruptioninoperationshoweverifboottimeofdatabaseishigh

viii)DirectoryonwhichDatabaseismountedmusthaveMultifactorAuthenticationMechanism
forstrongersecuritypolicy

ix)PrivateVPNshouldbeusedwhereeverpossible

x)AccesstoTrafficmustbewhitelistedonlyforcertainIPaddressofhostsystems

ThemostcosteffectiveonewouldbeimplememtingMFA,strongsecuritypoliciesandusing
256bitAESencryption

3)TheGriffithPocliyaddressesthefollowing

Theintegrityandvalidityofinformation
TheprotectionofUniversityassetsusingauthenticationmechanisms

Thepocilcydoesntaddressalltheissuesjustbecauseitsaysprotectionofunibersityassets.

Wedontknowwhatkindofauthenticationandsecuritymechanismareimplaceandwhich
peoplehaveaccesstowhatcontrolsandsystems

Thepolicymustclearlyspecifythetypeofauthenticationusedandwhohasaccesstowhatto
avoidconfusion

1)DescribethepermissionofpingandhowdoyouknowifitsisSetUIDProgram

[Link]
[Link]:

i)UsingthePasswdCommand

ii)UsingCronTabandAtCommand

WecancheckifSetUIDissetbytypingthefollowingcommandinterminal
Chmodu+[Link]//myfileisasamplefileIcreated

lsl//lsisusedtolistfiles

ThiscommandcanbeusedtocheckifauserAinownerpermissionfieldisreplacedbysor
S

[Link]

BeforeusingSUIDbit

AfterusingSUIDbit
2)Describeyourobservation

Beforeusingsudochmodus/bin/pingwecanseepingworks

Afterusingsudochmodus/bin/ping

ThisisbecausepingneedstogenerateandreceiveICMPpackets,andusuallythat'sdone
using"rawsockets"afeaturelimitedtoroot(cap_net_raw)becauseitcouldalsobeabused
tosniffanddisruptothertrafficonthesystem.

Manydistributionsnowjustgivepingthecap_net_rawprivilegeinsteadoffullsetuidroot.
Thishoweverneedsboththekernelandthefilesystemtosupportextendedattributes(xattrs),
andsome"minimal"systemsdisablethose.

3)Describeyourobservation

Usingsudo setcap cap_net_raw=ep /bin/ping we


Wehaveaddedacapabilitytopinginbinaryfolderwhichallowspingpermissiontoopenaraw
socketallowingtotargetapingsystem

Note:Ihavenotaddedscreenshotoflastcommandduetoitssecurityimplicsationsofthe
[Link]

4)/usr/bin/passwdistofacilitatechangingofuser'[Link],
theuserwillnotbeabletologinbutwillbeableto(orputtingitmorecorrectly,alwaysbe
forcedto)changehis/hberpasswordateveryloginattempt

Common questions

Powered by AI

Clearly defining access controls and who can access systems is critical to preventing unauthorized misuse or data breaches. Vague policies lead to confusion and potential security gaps, as the specific authentication and access rights are not clearly communicated, risking exposure of sensitive information .

Improper ACL configurations can grant unintended access to users, leading to potential data breaches and unauthorized actions within a system. Organizations can prevent such issues by implementing clear privilege specifications, regularly reviewing access levels, and enforcing strict access policies .

MFA provides stronger security by requiring multiple forms of verification before access is granted, reducing the likelihood of unauthorized access. For database protection, it ensures that even if one factor is compromised, additional layers prevent easy database exploitation .

The 'ping' command requires root-level permission to generate and receive ICMP packets via raw sockets, typically achieved through Set-UID, which can pose a security risk as it grants elevated privileges . An alternative uses capabilities like 'cap_net_raw', limiting 'ping' to necessary permissions, thus reducing security risks associated with full Set-UID root privileges .

256-bit AES encryption offers strong protection against data breaches by making decryption computationally infeasible, providing high security for sensitive data. However, it can introduce performance overheads and increase complexity in key management, potentially challenging for organizations to efficiently implement .

While an alarm system can prevent unauthorized access by shutting down the database, it may disrupt legitimate operations, especially if boot times are lengthy. Considerations include operational impact, the likelihood of false positives, and the ability to recover and log unauthorized access attempts .

XSS attacks can be mitigated by validating input, using content security policies, and properly escaping output in web applications. The effectiveness of XSS attacks depends on the attacker's programming skills and the application's susceptibility to accepting malicious scripts .

Poor password management policies without biometric authentication increases the risk of unauthorized access, potentially allowing SQL injection attacks to alter records, leading to erroneous organizational insights . To mitigate these vulnerabilities, implementing proper authentication mechanisms and using biometric security to restrict access are recommended .

Granting identical privileges to all users increases risk by enabling any user to access sensitive data or critical functions, elevating the potential for misuse or accidental damages. Addressing this involves implementing role-based access control (RBAC) to tailor privileges according to user roles and responsibilities .

Allowing SQL execution without security measures leads to vulnerabilities like SQL injection, enabling data extraction or manipulation by attackers. Risks can be mitigated by adopting strong encryption policies, ensuring proper input validation, and employing secure coding practices .

You might also like