Protection

Standard	Definition	Algorithm	Suggested Use
WEP	Wireless protocol that provides privacy similar to a wired network.	RC4	Basic security used for wireless networks.
WPA	Wireless protocol used for all devices.	RC4 & TKIP	Secure network for all types of devices.
WPA2	Wireless protocol created to fix security holes of WEP.	Full Standard	Secure network for newer devices.

 Temporal Key Integrity Protocol (TKIP) was employed and utilized to help strengthen the original basic WEP encryption.  TKIP utilizes a 128-bit wrapper around WEP encryption using a key which is normally based on MAC addresses and serial number of the packet being sent and received.  This addition allowed backwards compatibility between devices, in order to replace WEP as it could now work with all types of hardware no matter the age.

In order to accomplish a secure wireless network by ensuring only authorized computers are allowed to connect, I would setup MAC address whitelisting.  With every computer that requires a connection to the network there is a MAC address associated with it.  I would configure the router to allow only devices with specific MAC addresses. 

Attack Name	Definition	Result
Rogue access point	An additional access point on a network that the user is unaware of.	Opens a back door to unwanted users who can manage the network.
Jamming	Blocks wireless signal of current network.	Inability to connect to wireless network.
Interference	Disruption of current wireless network.	Can decrease wireless signals strength.
Bluejacking	Illegal activity that sends unsolicited messages to another Bluetooth device.	Unwanted pop-up messages on screen.
Evil twin	Rogue access point pretending to be another.	Obtains data once user connects to access point.
Replay attack	Spying on information that is sent between two people.	Obtains data between users and illegally uses it.

The three cloud computing service models readily available are (SaaS) Software as a Service, (PaaS) Platform as a Service, (IaaS) Infrastructure as a Service.  Starting with software as a service is the ability of a consumer to use the provider’s application and it cannot be managed or controlled.  Secondly, platform as a service is the consumer’s ability to deploy the provider’s applications to users but they are still unable to manage or control it.  Lastly, infrastructure as a service, which allows the consumer to provision, deploy, and run the provider’s application, but they are still unable to manage or control it.

The delivery models for cloud computing are as follows, private, public, community, and hybrid cloud.  Starting with a private cloud, this would be a cloud owned by the company or organization and they can be the provider and consumer.  For example, the company could not only deploy, provision, and run the application but they could also manage and control it. 

Secondly, the public cloud is open for use by the public which allows it to be managed, owned, and even operated by a company.  For example, google mail can be used for personal reasons or a business can utilize it for their own needs and incorporate it into their system.  Even though it’s being used by the company, the service still exists on the premises of the cloud provider (Dulaney & Easttom, 2014). 

Thirdly, a community cloud which is provisioned for a specific community.  For example, the community cloud is similar to a timeshare, even though you own it for a specific time period you share the maintenance.  Lastly, the hybrid cloud which is a combination of two or more available cloud infrastructures.  For example, combining both public and private cloud computing would allow flexibility when users are not on the network, but still require access to all their data.

The following five topics describe important concepts for virtualizations: Snapshots, Patch Compatibility, Host Availability/Elasticity, Security Control Testing (SCT) and Sandboxing. Briefly define each of these and explain why it can be a security concern.

Virtualization contains many topics such as snapshots, patch compatibility, host availability, security control testing and even sandboxing.  Work with virtual servers I have become very familiar with snapshots, as they can be extremely helpful when preparing for an upgrade.  A snapshot allows the end user to take an image of the server in its current state, so if something were to happen during an upgrade there is a good image to rollback to.  Although this may seem to be very useful, if these images are not stored in a safe place they can be used maliciously. 

Patch compatibility within virtualization, is the ability to ensure the stability as the preceding update.  One of the security concerns with patch compatibly is receiving a patch from an untrusted source and unknowingly applying that patch.  Host availability, is the ability to ensure if a host goes down you can eliminate down time and provide an available host almost immediately.  A security concern with host availability is the timeframe of which the host is down another twin host taking its place, if one was not provided quickly enough. 

Security control testing allows the end user to easily look for any weaknesses.  One of the main security concerns when using security control testing, is when security is pushed to the side in favor of the design (Dulaney & Easttom, 2014).  Sandboxing is the ability to run applications in a controlled memory areas, which reduces the likelihood of an application crashing.  Even though this can reduce the likelihood of the application crashing it is still possible, so testing is recommended.  The number one security concern with sandboxing is the application crashing while data is being inputted, which puts this data at risk.

References

Dulaney, E., & Easttom, C. (2014). CompTIA Security+ Study Guide, Sixth Edition. Indianapolis: John Wiley & Sons,.

Sales Force. (2016). Retrieved from Salesforce.com

Wireless attacks and its types. (n.d.). Retrieved December 11, 2016, from Exam Collection: http://www.examcollection.com/certification-training/security-plus-wireless-attacks-and-their-types.html