Network management concerns discussed

Introduction
Administrators of networks want to make sure that data resources have fast, secure and reliable access this can prove quite a challenge if areas such as security, performance and reliability is overlooked. Expanding onto this administrators may use applications on secure data centers that inspect all incoming traffic to enforce a filtering and security policy. The delivery of application resilience, high availability and tolerance to errors. The achievement of data center application delivery optimization and fault tolerance by striving to a maximum standard.

☀http://www.networkworld.com/article/2201555/tech-primers/the-network-s-role-in-improving-application-security--reliability-and-efficiency.html

About
Network connectivity is required on most devices and software applications that are used by individuals and businesses. One major point to address in network management concerns is planning ahead. A network manager before they begin to configure routers and switches must get an idea of how many devices may need IP addresses on the network. Additionally they must then plan ahead for other multiple devices that might be added gradually throughout time. This is to avoid a slow network performance if there is a lack of bandwidth etc. in the network.

Also using conventions is important. If the user sets up networks in the same way they will be easier to manage and troubleshoot. Here are points- http://searchitchannel.techtarget.com/feature/How-to-set-up-a-network-to-optimize-perAnoterformance-and-reliability
 * "Use a valid C-class network. 192.168.x.0 /24 (255.255.255.0) is a valid network according to networking conventions and standards. Althoughyou can use 10.0.0.0 /24 subnets and the like for the LAN, it is technically incorrect.
 * Set up DHCP to start and end on a certain range of IP addresses. Unless you have a unique situation, have the DHCP lease address range between .100 and .254. This way if you ever need to set up a static device, there is no question it needs to go below .100.
 * Logically group static devices within a certain IP range. For example, set network-related devices in the .1 through .10 range. Put servers between .11 and .20, network printers between .21 and .30, etc. This way you can effectively add and find statically set devices on the network, without knowledge of the exact address.
 * Use the same nontrivial passwords for administrative devices on a given network. It saves time and headache to be able to go to four completely different network devices and use the same username and password to log in. It saves time and headache. However, it should go without saying, different networks and different customers should absolutely have different passwords for the sake of security."

Another thing that can be done is by implementing firewalls for additional security measures. Fire walls can block out significant threats. In a network environment most routers will have routers on them but a lot of the time due to extra management and configuration it is usually disabled.

Intrusion detection systems are easy to install on a network and what they're built for is picking up all network traffic even if it isn't meant for the network card. A sniffer system is attached to a database what may be known as a target to attack and the IDS (intrusion detection system) will analyse each data packet. IDs can update firewalls automatically without just alerting the network admin. Additionally a feature called session sniping can be used which fools both connection points into shutting down so an attack won't be completed. IDS do have downsides and that they may generate loads of false positives, which is essentially triggering false alarms. If the IDS constantly sees traffic which is legitimate and blocks it as it sees it as a threat a system admin may shut it down leading to attacks which might get through.

http://searchnetworking.techtarget.com/tutorial/Network-security-lesson-2-Common-security-measures

Business insider has some great recommendations for helping to secure networks as well.

Data back ups

☀Scheduling regular backups to an external hard drive, or in the cloud, is a painless way to ensure that all your data is stored safely.

The general rule of thumb for backups: servers should have a complete backup weekly, and incremental backups every night; personal computers should also be backed up completely every week, but you can do incremental backups every few days if you like ("however long you could live without your data," Cloutier explains).

Getting your data compromised is a painful experience -- having it all backed up so you don't completely lose it will make it much less so.

Careful with email, IM and web browsing

It's not uncommon for a unsuspecting employee to click on a link or download an attachment that they believe is harmless -- only to discover they've been infected with a nasty virus, or worse.

''"Links are the numbers one way that malware ends up on computers," says Cloutier. "Links are bad!"''

As such, never click on a link that you weren't expecting or you don't know the origination of in an email or IM.

''You have to "be smart when surfing the Web," Watchinski warns. "[You] should take every “warning box” that appears on [your] screen seriously and understand that every new piece of software comes with its own set of security vulnerabilities."''

http://www.businessinsider.com/10-essential-data-security-measures-every-business-should-take-2010-6?op=1&IR=T

Viruses and malware also can v=have detrimental effects to general network performance.

Common signs of a virus include: These should not be regarded as definitive proof of infection, but as a warning that further checks should be made.
 * your system slowing down
 * unexpected activity on your machine or pop-up messages
 * your email server becoming overloaded or slowing down
 * data files becoming corrupt or going missing
 * unexpected changes in the content of your files

If a virus has infected your system, there are five basic steps for recovery:
 * Tell everyone who needs to know . If the virus is spread through email, inform everyone with an email account on the infected system as quickly as possible. If there is a specific file attachment that contains the malicious virus program, name it.
 * Quarantine infected machines . As soon as possible, disconnect infected computers from any internal or external networks. Do not reconnect until the virus is cleared.
 * Organise a clean-up operation . Use your anti-virus software to scan all computers and files to check whether the virus has spread. If necessary, contact your software supplier for specific advice.
 * Make sure there are no re-infections . Inform everybody what to do and what not to do. Maintain emergency security measures until the clean-up is complete and additional patches are in place to prevent re-infection.
 * Manage outgoing email traffic during the crisis . Use whatever facilities you have to prevent transfer of the virus via email. Consider closing down the outgoing mail service.

https://www.nibusinessinfo.co.uk/content/virus-identification-and-recovery