From the course: CompTIA Security+ (SY0-701) Cert Prep
Business continuity controls
From the course: CompTIA Security+ (SY0-701) Cert Prep
Business continuity controls
- [Narrator] Business continuity professionals have a variety of tools at their disposal to help remediate potential availability issues. One of the critical ways that IT professionals protect the availability of systems is ensuring that they're redundant. That simply means that they're designed in a way that a failure of a single component doesn't bring the entire system down. Business can continue in the face of a single, predictable failure. The single point of failure analysis process provides security professionals with a mechanism to identify and remove single points of failure from their systems. Let's look at an example. Here we have a simple web-based application, a web server protected by a firewall and connected to the internet. As we conduct a single point of failure analysis, we might first notice that the web server itself is a single point of failure. If anything goes wrong with that server, the web servers will stop functioning. We can correct the situation by replacing the single web server with a clustered farm of servers that are all designed to provide the same web service. The cluster is designed so that if a single server fails, the other servers will continue providing service without disruption. Once we've implemented the cluster, we've removed the server as a single point of failure. Next, we might turn our attention to the firewall, another single point of failure. If the firewall goes down, internet users will not be able to reach the web server, rendering the web service unavailable. Therefore, the firewall is also a single point of failure. We can correct that situation by replacing the firewall with a pair of high-availability firewalls, where one serves as a backup device, standing by to step in immediately if the primary firewall fails. By replacing the single firewall with a high-availability pair, we've removed the firewall as a single point of failure, but we have still yet another single point of failure here, the internal and external network connections. As with the web server and firewall, we can address this single point of failure by introducing redundancy and having two separate network connections for each link. If one fails, the service may continue to operate over the other. This single point of failure analysis may continue on identifying and remediating issues until either the team stops finding new issues, or the cost of addressing issues outweighs the potential benefit. This single point of failure analysis is an important part of an organization's continuity of operations planning efforts. Organizations should also consider the other risks facing their IT operations. As they conduct IT contingency planning, they should not only consider single points of failure, but also all the other situations that might jeopardize business continuity. For example, these might include the sudden bankruptcy of a key vendor, the inability to provide computing or storage capacity needed by the business, utility service failures, and any other risk that IT management believes may disrupt operations. And one final component of business continuity planning that's often overlooked is personnel succession planning. IT depends upon highly-skilled team members who develop, configure and maintain systems and processes. IT leadership should work with their human resources department to identify the team members who are essential to continued operations, and identify potential successors for those positions. That way when someone leaves the organization, management has already thought through potential replacements, and hopefully provided those successors with the professional development opportunities that they need to step into the departing employee's shoes.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
Contents
-
-
The goals of information security2m 11s
-
Authentication, authorization, and accounting (AAA)3m 31s
-
Categorizing security controls5m 11s
-
Conducting a gap analysis2m 34s
-
Zero Trust5m 32s
-
Physical access control4m 40s
-
Physical security personnel2m 12s
-
Deception technologies2m 55s
-
Change management6m 2s
-
-
-
Trust models2m 52s
-
PKI and digital certificates4m 5s
-
Hash functions7m 38s
-
Digital signatures3m 50s
-
Digital signature standard1m 27s
-
Create a digital certificate4m 55s
-
Revoke a digital certificate1m 28s
-
Certificate stapling2m 29s
-
Certificate authorities6m 13s
-
Certificate subjects3m 35s
-
Certificate types2m 55s
-
Certificate formats2m 30s
-
-
-
Preventing SQL injection4m 25s
-
Understanding cross-site scripting3m 17s
-
Request forgery4m 8s
-
Overflow attacks3m 21s
-
Explaining cookies and attachments4m 7s
-
Session hijacking4m 8s
-
Code execution attacks2m 43s
-
Privilege escalation1m 56s
-
OWASP Top Ten4m 45s
-
Application security4m 3s
-
Defending against directory traversal3m 4s
-
Race condition vulnerabilities2m 13s
-
-
-
Restricting network access2m 8s
-
Network access control4m 30s
-
Router configuration security4m 5s
-
Switch configuration security3m 42s
-
Maintaining network availability2m 32s
-
Network monitoring3m 41s
-
SNMP2m 54s
-
Isolating sensitive systems2m
-
Zero trust networking4m 9s
-
Secure access service edge (SASE)3m 50s
-
-
-
Operating system security8m 44s
-
Malware prevention7m 25s
-
Application management3m 46s
-
Host-based network security controls7m 44s
-
File integrity monitoring4m 9s
-
Data loss prevention5m 17s
-
Data encryption5m 39s
-
Hardware and firmware security5m 24s
-
Linux file permissions4m 2s
-
Web content filtering1m 47s
-
-
-
What is vulnerability management?5m 2s
-
Identify scan targets4m 24s
-
Scan configuration5m 20s
-
Scan perspective4m 24s
-
Security Content Automation Protocol (SCAP)2m 27s
-
Common Vulnerability Scoring System (CVSS )3m 31s
-
Analyzing scan reports4m 37s
-
Correlating scan results2m 20s
-
Vulnerability response and remediation2m 14s
-
-
-
Authentication factors3m 26s
-
Multifactor authentication2m 17s
-
Something you have4m 24s
-
Password policy4m 19s
-
Password managers2m 3s
-
Passwordless authentication3m 23s
-
Single sign-on and federation3m 9s
-
Kerberos and LDAP5m 18s
-
SAML2m 35s
-
OAUTH and OpenID Connect2m 55s
-
Certificate-based authentication5m 25s
-