AWS Security explained, why Enterprises, Governments and Institutions like it.

 

AWS Security Explained

 

Why Enterprises, Governments and

Institutions like it.

 

 

 

The above video from AWS Invent 2014 gives you good insight in AWS security features:

 

Download whitepapers written by AWS experts on a variety of cloud security and compliance topics:

 

Benefit_Version-Control_Blue

 

Watch AWS security experts and customers describe how AWS stays secure and how you can use AWS services and features to improve your security:

Benefit_Storage_Yellow

All AWS Security certifications (as off Q4 2014):

• Cloud Security Alliance — STAR Registrant

• DIACAP

• FedRAMP (FISMA ATO Moderate)

• FIPS 140-2

• HIPAA

• ISO 27001: 2005

• ITAR

• PCI DSS Level 1

• SOC 1 Type 2

• SOC 2 Type 2

• SOC 3

 

AWS is positioned as a leader on security for their Public Cloud Services offerings (Source Forrester Research).

 

 

 

 

 

Actions required to prepare for Postini End of Life

 

Actions required to prepare for Postini End of Life (EOL)

 

Google Postini EOL

 

As of June 15, 2015, Google will halt all mailflow through Postini systems. We are sending all migrating customers email notifications regarding steps required to prevent mailflow issues on or after that date. We explain those actions here.

Note for GMD customers: Even if the GMD phase of your transition has not completed, the changes below must be made as Google Apps supports mail filtering and archiving during GMD transition. You’ll continue to have access to your archive until 30 days after your GMD transition completes.

Starting on June 15, 2015, Google will take the following action(s) that will affect your service:

Disable Exchange Journaling through Postini. If you’re a GMD customer using Exchange Journaling, and you haven’t configured your server to forward journal messages to Google Apps Vault, your Journal deliveries will fail and your mail will not be archived.

Temporarily redirect all Postini DNS records for inbound mail to point at Google Apps. If you haven’t migrated to Google Apps, your inbound mail will be rejected. Even if you’ve migrated to Google Apps, you should update your MX records to point to Google Apps to avoid mailflow problems in the future.

Modify Postini Outbound mail routing and DNS records. If you’re a Google Apps customer—They’ll end support for mail routing through Postini Outbound service. Google Apps customers who are still sending traffic to the Postini Outbound service will have their Outbound Gateway setting adjusted to remove Postini Outbound.

If you have a non-Google Apps system—If you have a local mail server configured to use Postini Outbound, they’ll temporarily redirect all Postini DNS records for Postini Outbound to point at the Google Apps SMTP relay service. If you haven’t migrated to Google Apps, your outbound mail will be rejected. Even if you’ve migrated to Google Apps, you should adjust your local server’s configuration so that you’re sending traffic directly to the SMTP relay service, not Postini Outbound, to avoid mailflow problems in the future.

All customers—We highly recommend that you check your SPF records to ensure that they include Google IPs for a better mail filtering experience. Incorrect SPF records could result in your mail being marked as spam by your recipients.

Contact G4Cloud for the right solution to migrate your mail smoothly.

 

 

 

 

 

 

 

 

 

  •  
  •  

  •  

     

  •