"Actually Secure." IT Protection-A Developing MS Theory: MS Degree Capella: Miss. Bayo Elizabeth Cary, AA, BA, MLIS
11-9-2017
Unit 5 Discussion 2 Response 1
Response from: Miss. Bayo Elizabeth Cary, AA, BA, MLIS
To: Facility Director
Director,
After
a recent audit of security controls and policies, it is clear that we have some
vulnerabilities that need to be remediated. Below is the list of
vulnerabilities and solutions for each of them.
Vulnerabilities:
1.
Unauthorized personnel attempting to
gain access using an employee access card
2.
Users password was written and posted
on desk
3.
Users leaving computer unattended
while logged on
4.
Employees leaving sensitive company
information on desk
5.
Employees leaving sensitive
information on top of filing cabinet
6.
Employees leaving sensitive
information in copier
7.
Employees not disposing of sensitive
information properly
8.
Employees leaving secure area doors
unlocked
9.
Employees propping open server room
door
10. Employees not following maintenance schedules ( outdated
fire extinguisher)
Solutions:
1.
Add photo of employee on access
cards, have security issue new access card & deactivate old card
2.
Have all employees with password
written down to reset password & be counseled on password management
3.
Adjust settings that after 60
seconds of inactivity the computer locks
4.
Counsel employees with sensitive
information left on desk & reinforce punishments for violating the handling
of sensitive information
5.
Same as number 4
6.
Place and label copiers for
sensitive information in restricted/secure area. Post sign saying to remove
original from copy machine
7.
Designate locate in a restricted
area to place shredder and give two employees in security the task of gathering
and disposing of waste daily.
8.
Upgrade to doors that will
automatically close, lock and beep if left open for more than 45 seconds
9.
Same as 8
10. Counsel employees that are responsible for performing
maintenance and have management perform regular checks to ensure employees are
performing their duties.
V/R
David
Response from: Miss. Bayo Elizabeth Cary, AA, BA, MLIS
I think the
list of violations, and the list of corrective solutions, are good corrections.
It depends on the level of security, that a business wants-what the security
measures, should be. There are: low, medium, and higher levels, of security,
that can be enacted-to be protected IT information. There are some basics, that
will always be necessary, such as: changing passwords, on a regular basis.
Businesses, must weigh, the required: costs, and time, for increasing IT
security measures-some levels of security, are outside of an average budget.
IT security
risks are real. There may be ways, to manage security risks, in a-cost-effective
ways, while still raising the security protocols, to the highest levels? I
think it would be, an interesting and useful thesis, for my MS degree, at
Capella-to engineer my own: “discounted,” high security, IT perimeters systems
(360 degrees), to test the: software, and other equipment-establishing-an
almost impenetrable barrier (Smith, 2005, p. 14). A question, a hypothesis,
becomes a respectable: “theory,” when a researcher proves, that the proposed,
is actually-possible:
First,
of the three things that are subject to certification (compliance)– people,
process, and product – product seems to be the most immediately relevant.
Second, if we focus on product, testing seems insufficient; as Dijkstra
famously noted, testing can reveal the presence flaws, but not their absence. (Mclean,
2007, p. 1)
I think that IT security, at the very root, is a working
experiment. The goal, and aim, will always be-full compliance, with all, US:
laws, statutes, rules, and regulations. What we read in class, is only “theory.”
The best part, about being a researcher, and studying at the graduate level, is
testing the theories, and then-creating my own solutions. Many IT specialists,
have come and gone, and sometimes-the reality of IT security: the improvements,
make the situations worse, and some of the improvements-only help a little. I
think, that I can offer something better, something fresher, and more
innovative: “Actually Secure.”
References
Heitmeyer, C., Archer, M., Leonard,
E., and McLean, J. (2007). Applying Formal Methods to a
Certifiably Secure Software System:
IEEE Transactions on Software
Engineering, forthcoming. Information and Technology Division, US Naval
Research Laboratory. ACM 978-1-59593-887-9/07/0011.
Smith, Randy Franklin. (2005). Defense-in Depth. Windows IT
Security. Vol. 5, No. 11. p. 13-15. Retrieved from www.windowsitpro.com/windowssecurity
Comments
Post a Comment