KML_FLASHEMBED_PROCESS_SCRIPT_CALLS

Archive for January 29th, 2013

 

Leverage Automation for your Private Network

Tuesday, January 29th, 2013 by

GoGrid has recently released some new features that improve on the customer experience using our private network.  Private Network Automation (PNA) is currently available in all our data centers. As of this most recent release, these new features will be exposed if you enable PNA by contacting support:

  • All servers will have a private IP assigned upon creation (both virtual and dedicated)
  • Any private IPs that are used will be marked as assigned on the portal
  • Cloud Storage no longer requires static routes. It is now accessible via your favorite protocol (Samba, SCP, etc.)

The assignment of private IPs happen automatically at the time a new server is deployed. GoGrid has enabled this for all new customers. If you are an existing customer, this is feature IS NOT enabled in data centers where you have servers deployed. You will need to file a support ticket to request this feature. Note that once enabled, this will be active for all new servers only – existing servers will keep their existing settings.

As you can see from the screenshot below, once you create the server, you will have a public IP and a private IP assigned. Note that this feature is enabled for both virtual and dedicated servers.

AMS_private_IP

This is also visible in the Networking tab so that you can monitor private IPs that have been assigned from your block.

PNA_List

(more…) «Leverage Automation for your Private Network»

How to Recover from a Linux Security Breach – Recovery & Hardening (Part 2)

Tuesday, January 29th, 2013 by

This is Part 2 of a GoGrid security blog series on identifying and recovering from a Linux security breach. Part 1 provided general guidelines for conducting a security analysis on a compromised Linux server and forming strategic teams to address and resolve the breach.

In this article, we’ll review some recommended steps for recovering from a breach.

Recovering from the Breach

Lock the doors

Now that you’ve confirmed that there are no intruders logged in and you’ve identified the established connections, it’s time to “lock the doors.” Locking the doors largely depends on who is managing your firewall. Contact GoGrid in the event that we’re managing your firewall or perform the following actions if you manage your firewall:

  • Modify your system’s iptables configuration to restrict all remote console connections such as SSH to your office network
  • Modify your system’s iptables configuration to block all previously identified suspicious connections from and to your system.
  • Modify your system’s iptables to block all other services from the public Internet to your server. Doing so will effectively bring down your website or services, but you want to avoid compromising your customers or web site visitors.

Install and run a rootkit analyzer

(more…) «How to Recover from a Linux Security Breach – Recovery & Hardening (Part 2)»