[vc_row full_width=”true” background_color=”#1f242a”][vc_column pl=”10″][vc_custom_heading text=”” font_container=”tag:h2|font_size:42|text_align:center|color:%23ffffff|line_height:2″ use_theme_fonts=”yes”][vc_row_inner content_placement=”middle”][vc_column_inner][vc_column_text]<\/p>\n
\n
\t\t\t\t Chief information officer <\/b><\/p>\n
Information Security Management System <\/b> These are the ways in which an ISO27k ISMS will typically benefit the organization. <\/p>\n<\/th>\n
<\/p>\n
Information security risk reduction <\/b> <\/p>\n <\/p>\n Benefits of standardization <\/b> <\/p>\n Being risk-based, the ISO27k approach is flexible enough to suit any<\/em> organization, as opposed to more rigid and prescriptive standards such as PCI-DSS \u2013 cost saving<\/strong><\/span>\n\t\t\t\t <\/p>\n <\/p>\n Benefits of a structured approach <\/b> <\/p>\n <\/p>\n Benefits of certification1<\/sup> <\/b> <\/p>\n Demonstrates management’s clear commitment to information security for corporate governance, compliance or due diligence purposes \u2013 cost saving and risk reduction<\/strong> <\/span>\n\t\t\t\t <\/p>\n <\/p>\n Benefits of compliance <\/b> <\/p>\n <\/p>\n Understanding the Goals of Information Security <\/b> <\/p>\n Like so many things, the goals of information security are straightforward. They create the framework that is used for developing and maintaining a security plan. They’re remarkably easy to express but extremely hard to carry out. These goals are as follows:\n<\/p>\n Prevention <\/strong>Prevention <\/em>refers to preventing computer or information violations from occurring; it is much easier to deal with violations before they occur than after. Security breaches are also referred to as incidents<\/em>. When an incident occurs, it may be the result of a breakdown in security procedures. Incidents come in all shapes and sizes. Simple incidents include things such as losing a password or leaving a terminal logged on overnight. They can also be quite complex and result Detection <\/strong>Detection <\/em>refers to identifying events when they occur. Detection is difficult in many situations; an attack on your system may occur over a long period before it’s successful. Incident detection involves identifying the assets under attack, how the incident occurred, and who carried it ut (or is still doing so). The detection process may involve a variety of complicated tools or a simple examination of the system log files. Detectionactivities should be ongoing and part of your information security policies and procedures.<\/p>\n Response <\/strong>Response <\/em>refers to developing strategies and techniques to deal with an attack or loss. Developing an appropriate response to an incident involves several factors. If the incident was a probe, the attacker may have done no actual harm but may be gathering intelligence about your etwork or systems. These types of attacks may be random or targeted, and they usually cause little damage. Occasionally, an attack will be successful. When that happens, it is helpful to have a well-thought-out and tested plan you can use to respond, restore operation, and neutralize the hreat. It’s always better to have a set of procedures and methods in place to recover from an incident than to try to create those processes on-the-fly. These goals are an important part of setting benchmarks for an organization. You can’t allow these policies or goals to become insignificant. If you do, you and your organization are setting yourselves up for a surprise. Unfortunately, the surprise won’t be pleasant, and it may be very costly to deal with.<\/p>\n<\/p>\n <\/p>\n Comprehending the Security Process <\/b> <\/p>\n \t It helps to think of security as a combination of three Ps: processes, procedures, and policies. The security of information involves both human and technical factors. The human factors are addressed by the policies that are enforced in the organization as well as the processes and procedures your organization has in place. The technology components include the tools you install on the systems you work with. There are several parts to this process, and each is described in the following sections.<\/p>\n<\/p><\/div>\n [\/vc_column_text][\/vc_column_inner][\/vc_row_inner][\/vc_column][\/vc_row] <\/p>\n <\/p>","protected":false},"excerpt":{"rendered":" [vc_row full_width=”true” background_color=”#1f242a”][vc_column pl=”10″][vc_custom_heading text=”” font_container=”tag:h2|font_size:42|text_align:center|color:%23ffffff|line_height:2″ use_theme_fonts=”yes”][vc_row_inner content_placement=”middle”][vc_column_inner][vc_column_text]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/pages\/3085"}],"collection":[{"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/comments?post=3085"}],"version-history":[{"count":18,"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/pages\/3085\/revisions"}],"predecessor-version":[{"id":3200,"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/pages\/3085\/revisions\/3200"}],"wp:attachment":[{"href":"https:\/\/atp.sa\/en\/wp-json\/wp\/v2\/media?parent=3085"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
\n
\n
\n in the involvement of local or federal law enforcement personnel. If a group of hackers were to attack and deface your website, you would consider this a major incident. Ideally, your security procedures and policies would make you invulnerable to an attack; unfortunately, this isn’t usually the case. The better your prevention policies, however, the lower the likelihoodof a successful attack occurring.<\/p>\n