<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Information Security Management on Bill Brown:Thoughts and Reference Material Online</title><link>https://www.billbrown.info/series/information-security-management/</link><description>Recent content in Information Security Management on Bill Brown:Thoughts and Reference Material Online</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>BillBrown.info</copyright><lastBuildDate>Thu, 30 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.billbrown.info/series/information-security-management/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Cloud Security Risks, Compliance, and Best Practices</title><link>https://www.billbrown.info/post/amazon-web-services-cloud-information-security-risks-and-compliance/</link><pubDate>Thu, 30 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/amazon-web-services-cloud-information-security-risks-and-compliance/</guid><description>
&lt;h2 id="amazon-web-services-cloud-information-security-risks-and-compliance"&gt;Amazon Web Services Cloud Information Security Risks and Compliance&lt;/h2&gt;
&lt;h2 id="abstract"&gt;Abstract&lt;/h2&gt;
&lt;p&gt;This paper examines the critical security considerations and compliance requirements for organizations migrating to Amazon Web Services (AWS) cloud infrastructure, addressing the widespread concerns among IT professionals regarding cloud security risks. The research explores AWS's Shared Responsibility Model as the fundamental framework for delineating security obligations between AWS and its customers, where AWS manages the security &amp;quot;of&amp;quot; the cloud infrastructure while customers maintain responsibility for security &amp;quot;in&amp;quot; the cloud. Through analysis of AWS's global infrastructure security services, the paper identifies key customer responsibilities including operating system security, data encryption, network configuration, and identity access management, while AWS maintains the physical infrastructure, hypervisor, and managed services.&lt;/p&gt;</description></item><item><title>Common Issues with Security Policy Implementation</title><link>https://www.billbrown.info/post/common-issues-with-security-policy-implementation/</link><pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/common-issues-with-security-policy-implementation/</guid><description>
&lt;h2 id="common-issues-with-security-policy-implementation"&gt;Common Issues with Security Policy Implementation&lt;/h2&gt;
&lt;h3 id="original-query"&gt;Original Query&lt;/h3&gt;
&lt;p&gt;Discuss common issues with implementation of security policies and Discuss include common issues and possible mitigations to ensure policy can be enforced.&lt;/p&gt;
&lt;h3 id="common-implementation-issues"&gt;Common Implementation Issues&lt;/h3&gt;
&lt;p&gt;&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
Implementation issues happen with security policies. Some of the common implementation issues, as described by Johnson (2014) are organization structure, fitting policies to leaders and targeting early adopters. The implementation of the policy has to take into account the type of organization, how large or small the organization is and what kind of technology is in use. One leader may present a security policy in a team meeting or town hall while another leader may be more hierarchical in the approach by holding a series of group meetings.&lt;/p&gt;</description></item><item><title>Incident Response Best Practices and AWS Forensic Procedures</title><link>https://www.billbrown.info/post/incident-response-process-best-practices-and-aws-forensic-procedures/</link><pubDate>Tue, 28 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/incident-response-process-best-practices-and-aws-forensic-procedures/</guid><description>
&lt;h2 id="incident-response-process-best-practices-and-aws-forensic-procedures"&gt;Incident Response Process Best Practices and AWS Forensic Procedures&lt;/h2&gt;
&lt;h3 id="topic-or-question"&gt;Topic or Question&lt;/h3&gt;
&lt;p&gt;&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
There are so many methods and best practices for handling incidents. Outline what an incident response process based on what is in the text. What is the process order, what may be missing, and how could the process be improved?&lt;/p&gt;
&lt;h3 id="introduction-to-incident-response-and-management"&gt;Introduction to Incident Response and Management&lt;/h3&gt;
&lt;p&gt;Incident response (IR) and Incident Management (IM) are similar when a disaster of any type occurs as described by Peltier (2013). IR and IM concepts document and developed and get utilized no matter why type of disaster that happened. The disaster could occur by computer security breach, a physical security attack or a natural disaster such as an earthquake.&lt;/p&gt;</description></item><item><title>Business Continuity and Disaster Recovery Planning Models</title><link>https://www.billbrown.info/post/compare-and-contrast-various-business-continuity-and-disaster-recovery-planning-models/</link><pubDate>Mon, 27 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/compare-and-contrast-various-business-continuity-and-disaster-recovery-planning-models/</guid><description>
&lt;h2 id="compare-and-contrast-various-business-continuity--disaster-recovery-planning-models"&gt;Compare and Contrast Various Business Continuity &amp;amp; Disaster Recovery Planning Models&lt;/h2&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Business continuity is essential as described by Hiles (2014). It is the ability of an organization to survive and thrive, survive and bounce back after a disaster or catastrophes. The general objective is to accomplish the mission for the organization no matter what disruptions happen along the way. Business continuity as described by Rima (2013) focuses on an organization's capacity to continue operations irrespective of the nature of interruption. The business continuity planning (BCP) which is a methodology that can be studied, and practitioners can be certified by Rima (2013) points out. The disaster recovery plan is considered a subset of BCP since it addresses stopping the effects of the disaster, catastrophe or event. After the consequences of the disaster or event have been resolved, business continuity activities typically begin. Business continuity as described by Hiles (2014) is the constant readiness of all necessary assets that support critical business functions. Business continuity management (BCM) offers the readiness of the process and resources following a disruption in the business to ensure the continued achievement of mission critical objectives.
&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
&lt;/p&gt;</description></item><item><title>BCP &amp; DR Planning: Common Approaches, Drawbacks, and Mitigations</title><link>https://www.billbrown.info/post/common-approaches-and-drawbacks-in-business-continuity-and-disaster-recovery-plans/</link><pubDate>Sun, 26 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/common-approaches-and-drawbacks-in-business-continuity-and-disaster-recovery-plans/</guid><description>
&lt;h2 id="common-approaches-and-drawbacks-in-business-continuity-and-disaster-recovery-plans"&gt;Common Approaches and Drawbacks in Business Continuity and Disaster Recovery Plans&lt;/h2&gt;
&lt;p&gt;&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
Business continuity is essential as described by Hiles (2014). It is the ability of an organization to survive and thrive, survive and bounce back after a disaster or catastrophes. The general objective is to accomplish the mission for the organization no matter what disruptions happen along the way. Business continuity as described by Rima (2013) focuses on an organization's capacity to continue operations irrespective of the nature of interruption. The business continuity planning (BCP) is a methodology that can be studied, and practitioners can be certified by Rima (2013) points out. A Disaster recovery plan is a subset of BCP since it addresses stopping the effects of the disaster, catastrophe or event. After the effects of the disaster or event have been addressed, business continuity activities typically begin.&lt;/p&gt;</description></item><item><title>Types of Security Architecture and Design Models Explained</title><link>https://www.billbrown.info/post/appraise-the-various-types-of-security-architecture-and-design-models/</link><pubDate>Sat, 25 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/appraise-the-various-types-of-security-architecture-and-design-models/</guid><description>
&lt;h2 id="appraise-the-various-types-of-security-architecture--design-models"&gt;Appraise the Various Types of Security Architecture &amp;amp; Design Models&lt;/h2&gt;
&lt;h3 id="security-architecture-overview"&gt;Security Architecture Overview&lt;/h3&gt;
&lt;p&gt;&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
Security architecture is the view of the overall system architecture from a security perspective. Security architecture provides insight into the security services, mechanisms, technologies, and features that can be used to satisfy system security requirements as described by Tipton &amp;amp; Krause (2003). The security architecture offers recommendations in the context of the overall system architecture, and security mechanisms should be placed. The security view of a system architecture emphases the system security services and mechanisms, implementation of security related functionality, and identifies interdependencies among security-related components, services, mechanisms, and technologies, and at the same time reconciling any conflict between them. The security architecture is one aspect of an enterprise or system architecture, and can also include network architecture or connectivity architecture.&lt;/p&gt;</description></item><item><title>Physical Security Failure Points and Mitigation Strategies</title><link>https://www.billbrown.info/post/common-points-of-failure-and-strategies-to-mitigate-physical-security-deficiencies/</link><pubDate>Fri, 24 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/common-points-of-failure-and-strategies-to-mitigate-physical-security-deficiencies/</guid><description>
&lt;h2 id="common-points-of-failure-and-strategies-to-mitigate-physical-security-deficiencies"&gt;Common Points of Failure and Strategies to Mitigate Physical Security Deficiencies&lt;/h2&gt;
&lt;h3 id="layered-defense-approach"&gt;Layered Defense Approach&lt;/h3&gt;
&lt;p&gt;&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
The nature of physical security ought to be like concentric rings or layers of defense with requirements for access that gets more difficult the closer one get to the center of the rings as described by Peltier (2013). The reason for the rings of security is evident because the security team takes some precautions to protect the organization.&lt;/p&gt;</description></item><item><title>Physical Security Models: Features and Functionality Compared</title><link>https://www.billbrown.info/post/evaluating-features-and-functionality-of-physical-security-models/</link><pubDate>Thu, 23 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.billbrown.info/post/evaluating-features-and-functionality-of-physical-security-models/</guid><description>
&lt;h2 id="evaluating-the-features-and-functionality-of-various-physical-security-models"&gt;Evaluating the Features and Functionality of Various Physical Security Models&lt;/h2&gt;
&lt;h3 id="three-levels-of-information-security"&gt;Three Levels of Information Security&lt;/h3&gt;
&lt;p&gt;&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="9168865232"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
Logical security, physical security, and premise security are the three levels of information security as described by Vacca (2013). Logical security protects data stored on computers from software and network threats. The physical safety or infrastructure security protects the information systems that store the data. Physical security must also protect the people who operate and maintain systems and those who use the data. Premises security normally entails protecting facilities security. Premise security protects the people and property within the facility or building(s) that make up the organization.&lt;/p&gt;</description></item></channel></rss>