You are here

Sistema

Contributed by Billy Short
Bring Your Own Device policies are becoming more common. Information Technology teams will have to ensure that they accommodate these growing movements. This document will help teams understand how the BYOD policy will change their network infrastructure, why BYOD is the future of network infrastructure, and the risks and possible consequences of implementing BYOD in an enterprise organization.

A demilitarized zone (DMZ) in terms of a network is a segmented area in the network that is available to the public but is segmented in order to stay separated from a network’s internal private network. In other words, it separates the untrusted public Internet from the trusted network of an organization. This is done through the act of subnetting and is a useful network security design feature within the network architecture.

Wearable technology has grown extremely popular. From smartwatches to glasses, there are a variety of wearables that are now available to consumers for various purposes. Most consumers purchase these devices for ease of data access. Smartwatches may be used to avoid having to pull out their phone to collect basic information such as the weather forecast or to quickly read a text message or calendar reminder. Activity trackers help one improve on their workout and assist in tracking performance over time. Smart glasses allow us to better document our trips and experiences to help share with friends and family. So what happens to the data collected by wearables?

Due to the nature of how BGP operates and how it was designed, a series of both unintentional mistakes or malicious attacks could take place to take down an entire autonomous system; or a more nefarious act of intercepting traffic and then routing it to the correct destination could also take place. In order to combat the trusting nature of BGP, a series of threat mitigation techniques have been implemented in order to protect BGP against attacks. This includes setting up BGP neighbor authentications, filtering BGP prefixes with AS path access lists, BGP time to live (TTL) security check, and the future resource public key infrastructure (RPKI) have been put in use.

As you read along you will learn much about the process in securing a database and all the elements or encounters you can and will face. The process in securing a database is complex; however, the potential harm from not properly securing a database is far greater.