Author: Benjamin D. Thomas
When addressing matters of information confidentiality, integrity, and availability, there
are four perspectives that can be taken when introducing security controls. A control
can be a protection, detection, response, or assurance mechanism. It is not uncommon
for a single control to provide information security on multiple levels.
Protection
A protection mechanism is used to prevent security incidents from occurring. Examples
of protection mechanisms include: firewall rules, access control lists, encrypting packets
that transverse over a network, passwords, biometrics, etc.
Detection
It is an information security mechanism that detects when an incident is occurring, and
allows a business to adjust its course of action. Detection mechanisms include:
intrusion detection systems, virus/spam scanners, vulnerability scanning, quotas, logging
alerts, etc. Detection mechanisms often lead into response mechanisms, and are often
the same as or similar to assurance mechanisms.
Response
A response mechanism addresses the consequences of a security incident and helps
the organization return to a normal state. Response mechanisms can either be in the
form of technical security controls (e.g. intrusion prevention system), policy (e.g.
requiring a computer emergency response team), or procedures developed for all
persons to follow during an incident.
Assurance
Assurance mechanisms give management or third parties the ability to verify the
effectiveness of the security controls in place. It may include logging, auditing, and
reporting capabilities. Assurance is important to help justify further expenditure on
information security projects.
Until next time, cheers!
Benjamin D. Thomas
LinuxSecurity.com
Feature Extras:Getting
to Know Linux Security: File Permissions – Welcome to the first
tutorial in the ‘Getting to Know Linux Security’ series. The topic explored
is Linux file permissions. It offers an easy to follow explanation of how
to read permissions, and how to set them using chmod. This guide is intended
for users new to Linux security, therefore very simple. If the feedback is
good, I’ll consider creating more complex guides for advanced users. Please
let us know what you think and how these can be improved.The
Tao of Network Security Monitoring: Beyond Intrusion Detection
– To be honest, this was one of the best books that I’ve read on network security.
Others books often dive so deeply into technical discussions, they fail to
provide any relevance to network engineers/administrators working in a corporate
environment. Budgets, deadlines, and flexibility are issues that we must all
address. The Tao of Network Security Monitoring is presented in such a way
that all of these are still relevant.Encrypting
Shell Scripts – Do you have scripts that contain sensitive information
like passwords and you pretty much depend on file permissions to keep it secure?
If so, then that type of security is good provided you keep your system secure
and some user doesn’t have a “ps -ef” loop running in an attempt to capture
that sensitive info (though some applications mask passwords in “ps” output).
Take advantage of our Linux Security discussion
list! This mailing list is for general security-related questions and comments.
To subscribe send an e-mail to security-discuss-request@linuxsecurity.com
with “subscribe” as the subject.
Thank you for reading the LinuxSecurity.com
weekly security newsletter. The purpose of this document is to provide our readers
with a quick summary of each week’s most relevant Linux security headline.
Contectiva | ||
Conectiva: ethereal Fixes for security vulnerabilities in ethereal |
||
28th, March, 2005
|
||
Conectiva: kernel Kernel fixes | ||
31st, March, 2005
|
||
Debian | ||
Debian: New netkit-telnet packages fix arbitrary code execution |
||
29th, March, 2005
|
||
Debian: New mc packages fix buffer overflow | ||
29th, March, 2005
|
||
Debian: New netkit-telnet-ssl packages fix arbitrary code execution |
||
29th, March, 2005
|
||
Debian: New mailreader packages fix cross-site scripting vulnerability |
||
30th, March, 2005
|
||
Debian: New samba packages fix arbitrary code execution |
||
31st, March, 2005
|
||
Fedora | ||
Fedora Core 2 Update: mozilla-1.7.6-1.2.2 | ||
25th, March, 2005
|
||
Fedora Core 3 Update: lsof-4.72-2.2 | ||
24th, March, 2005
|
||
Fedora Core 3 Update: selinux-policy-targeted-1.17.30-2.90 | ||
24th, March, 2005
|
||
Fedora Core 3 Update: thunderbird-1.0.2-1.3.2 | ||
24th, March, 2005
|
||
Fedora Core 2 Update: epiphany-1.2.10-0.2.1 | ||
25th, March, 2005
|
||
Fedora Core 2 Update: devhelp-0.9.1-0.2.5 | ||
25th, March, 2005
|
||
Fedora Core 2 Update: kernel-2.6.10-1.771_FC2 | ||
28th, March, 2005
|
||
Fedora Core 3 Update: squirrelmail-1.4.4-1.FC3 | ||
28th, March, 2005
|
||
Fedora Core 2 Update: squirrelmail-1.4.4-1.FC2 | ||
28th, March, 2005
|
||
Fedora Core 3 Update: spamassassin-3.0.2-0.fc3 | ||
28th, March, 2005
|
||
Fedora Core 2 Update: mozilla-1.7.6-1.2.5 | ||
29th, March, 2005
|
||
Fedora Core 2 Update: sylpheed-1.0.4-0.fc2 | ||
29th, March, 2005
|
||
Fedora Core 3 Update: sylpheed-1.0.4-0.fc3 | ||
29th, March, 2005
|
||
Fedora Core 2 Update: krb5-1.3.6-4 | ||
29th, March, 2005
|
||
Fedora Core 3 Update: krb5-1.3.6-5 | ||
29th, March, 2005
|
||
Fedora Core 3 Update: xorg-x11-6.8.2-1.FC3.13 | ||
29th, March, 2005
|
||
Fedora Core 2 Update: xorg-x11-6.7.0-14 | ||
29th, March, 2005
|
||
Fedora Core 3 Update: system-config-services-0.8.21-0.fc3.1 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: telnet-0.17-32.FC3.2 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: foomatic-3.0.2-13.3 | ||
30th, March, 2005
|
||
Fedora Core 2 Update: squid-2.5.STABLE9-1.FC2.2 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: squid-2.5.STABLE9-1.FC3.4 | ||
30th, March, 2005
|
||
Fedora Core 2 Update: telnet-0.17-28.FC2.1 | ||
30th, March, 2005
|
||
Fedora Core 2 Update: ImageMagick-6.2.0.7-2.fc2 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: ImageMagick-6.2.0.7-2.fc3 | ||
30th, March, 2005
|
||
Fedora Core 2 Update: gdk-pixbuf-0.22.0-12.fc2 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: gdk-pixbuf-0.22.0-16.fc3 | ||
30th, March, 2005
|
||
Fedora Core 2 Update: gtk2-2.4.14-2.fc2 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: gtk2-2.4.14-3.fc3 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: initscripts-7.93.7-1 | ||
30th, March, 2005
|
||
Fedora Core 3 Update: selinux-policy-targeted-1.17.30-2.93 | ||
30th, March, 2005
|
||
Gentoo | ||
Gentoo: mpg321 Format string vulnerability | ||
28th, March, 2005
|
||
Mandrake | ||
Mandrake: Updated krb5 packages fix | ||
29th, March, 2005
|
||
Mandrake: Updated ipsec-tools packages | ||
31st, March, 2005
|
||
Mandrake: Updated libexif packages fix | ||
31st, March, 2005
|
||
Mandrake: Updated htdig packages fix | ||
31st, March, 2005
|
||
Red Hat |
||
RedHat: Moderate: grip security update | ||
28th, March, 2005
|
||
RedHat: Important: telnet security update | ||
28th, March, 2005
|
||
RedHat: Important: mysql security update | ||
28th, March, 2005
|
||
RedHat: Important: krb5 security update | ||
30th, March, 2005
|
||
RedHat: Moderate: XFree86 security update | ||
30th, March, 2005
|
||
SuSE | ||
SuSE: several kernel security problems | ||
24th, March, 2005
|
||
SuSE: MySQL vulnerabilities | ||
24th, March, 2005
|
||
SuSE: ipsec-tools remote denial of service | ||
31st, March, 2005
|
||