Find Resources & Connect with members on topics that interest you.

AI - Acquire and Implement

PO - Plan and Organize

DS - Deliver and Support

Please sign in to see your topics.

You must be logged in to join this group.

DS5.9 - Malicious Software Prevention, Detection and Correction

This topic is intended to enable collaboration and sharing of information to facilitate a better understanding and approach to implementing this COBIT control objective based on the risk, value and guidance provided by its corresponding control practices.

COBIT Control Objective DS5.9 - Malicious Software Prevention, Detection and Correction is contained within Process Popup Ensure Systems Security.

Learn more about COBIT and related publications.

Click “Join This Community” to be able to actively participate in discussions and contribute content. You must be an ISACA member to join this topic. Join ISACA now.

 
This Topic Has:
6 Members
0 Online
794 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Points: 3


Malicious Software Prevention, Detection and Correction

Put preventive, detective and corrective measures in place (especially up-to-date security patches and virus control) across the organisation to protect information systems and technology from malware (e.g., viruses, worms, spyware, spam).

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • System security ensured by proactive malware protection
  • Ensured system integrity
  • Timely detection of security threats
  Risk Drivers
  • Exposure of information
  • Violations of legal and regulatory requirements
  • Systems and data that are prone to virus attacks
  • Ineffective countermeasures

View Control Practices  help

Hide Control Practices  help

  1. Establish, document, communicate and enforce a malicious software prevention policy in the organisation. Ensure that people in the organisation are aware of the need for protection against malicious software, and their responsibilities relative to same.
  2. Install and activate malicious software protection tools on all processing facilities, with malicious software definition files that are updated as required (automatically or semi-automatically).
  3. Distribute all protection software centrally (version and patch-level) using centralised configuration and change management.
  4. Regularly review and evaluate information on new potential threats.
  5. Filter incoming traffic, such as e-mail and downloads, to protect against unsolicited information (e.g., spyware, phishing e-mails).

 

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 76 total

Events & Online Learning: 13 total

7 May 2012
ISACA International Event
Orlando, Florida, USA
Get the knowledge you need to stay one step ahead of the competition and keep up with changing professional trends at ISACA’s North America CACS Conference.
14 May 2012
ISACA International Event
Chicago, IL, USA
15 May 2012
ISACA International Event
Washington, DC, USA
12 Jun 2012
ISACA International Event
Dallas, Texas, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.
7 Aug 2012
ISACA International Event
Chicago, Illinois, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.

Journal Articles: 260 total

Volume 3, 2012
by Steven J. Ross, CISA, CISSP, MBCP
To accelerate investments in security, we security professionals must do a better job of communicating the reality of the threats that our organizations face.
Volume 3, 2012
by Fabrizio Baiardi, Claudio Telmon, CISA, CISSP, and Daniele Sgandurra, Ph.D.
Haruspex is a risk evaluation methodology defined and implemented by the research group on risk management in the Department of Computer Science at the University of Pisa, Italy.
Volume 2, 2012
by Ed Gelbstein, Ph.D.
In the last couple of years, it has become evident that no organization can avoid being influenced by the tsunami of innovative technology, with ever shorter life cycles.
Volume 1, 2012
by Michael Mendelsohn, CISSP, Antoine Philipovitch, William Welch, CISM, and Robert Zanella, CISA
One of today’s big security marketing pushes is enterprise single sign-on (ESSO).
Volume 1, 2012
by Edward Amoroso | Reviewed by Jeimy J. Cano M., Ph.d., CFC, CFE, CMAS
This book is particularly interesting to and useful for information security and IT governance professionals because of its strategic and tactical guidance that can help refine decisions on the protection of critical infrastructure.
Volume 6, 2011
by Ed Gelbstein, Ph.D.
Information security has become a visible issue in business, on the move and at home.

Wikis: 2 total

Blog Posts: 26 total

On the AS/400 (System i) it is possible to audit for default passwords using the ANZDFTPWD command. A default password is defined as a password which is the same as the user profile. The command behaves slightly differently depending on the value of the s...
Posted By : Ian Cooke | 0 comments
The main idea I am trying to advocate with these posts is a simple one.  Compare a database you are auditing against a database that you know already meets the standards required by the organisation you are auditing. This is achieved by creating “CSV ty...
Posted By : Ian Cooke | 1 comments
We have covered most of the core items that should be consider when performing an Oracle database audit in previous posts, however there a number of other items that I would typically look into. Database Links A database link is an object in one database...
Posted By : Ian Cooke | 0 comments
The company you are auditing should have a policy on what is being audited within your Oracle database.  The level of auditing will almost certainly be affected by the sensitivity of the data. Good examples and bench marks for auditing may be seen in the...
Posted By : Ian Cooke | 0 comments
Typically application access to an Oracle database is via one of two methods.  Either all users access the same database using a single (proxy) user which is defined in an initialisation (.INI) file, registry etc. Or the users access the database individ...
Posted By : Ian Cooke | 1 comments
Before we get into auditing Oracle privileges a reminder of a few definitions might be helpful. A user privilege is the right to run a particular type of SQL statement, or the right to access an object belonging to another user, run a PL/SQL package, and...
Posted By : Ian Cooke | 1 comments