How to encrypt your Kindle Fire HDX

Beyond just using a PIN code lock screen, Amazon's Kindle Fire HDX and HDX 8.9-inch tablets can also be secured with device encryption.

Device encryption can be a great way to keep your data secure in case it falls into the wrong hands. For many users, however, it can be overkill and there's usually a performance hit to a device that's been encrypted. Using a PIN code to lock the device is usually an effective deterrent and software tools like Find My iPhone and Android Device Manager can help track, lock, or wipe lost devices.

Unfortunately for Kindle Fire HDX owners, there's no app available that's comparable to Find My iPhone or Android Device Manager. If you want to be extra cautious with your data or if you're using a Kindle Fire HDX in an enterprise environment, here's how to encrypt it:

Step 1: Make sure you have the latest version of Fire OS installed, then fully charge your Kindle Fire HDX.

Step 2: With your Kindle Fire HDX plugged in to a wall charger, go to Settings > Security, then select Encryption.

Step 3: Tap on the "Encrypt tablet" button. If your Fire HDX isn't fully charged or plugged in, you won't see this option.

Step 4: If you have a PIN, you'll need to enter it, then set an encryption password. This password is different than your lock screen PIN. It will be used only when you boot up the Kindle Fire HDX.

Step 5: After you've entered your encryption password, tap the "Continue" button to begin the encryption process.

Your Kindle Fire HDX will reboot, then begin encrypting. Depending on the amount of data stored on your Kindle Fire HDX, the process could take up to an hour to complete, though our test Kindle only took 12 minutes.

Keep in mind that there's no way to decrypt your Kindle Fire HDX once it's been encrypted. To remove the encryption, you'll have to perform a factory reset and erase all your data. Additionally, if the wrong encryption password is entered 30 consecutive times, your Kindle Fire HDX will automatically be reset to factory defaults and your data erased.

Original post:
How to encrypt your Kindle Fire HDX

[DEFCON 21] Protecting Data with Short-Lived Encryption Keys and Hardware Root of Trust – Video


[DEFCON 21] Protecting Data with Short-Lived Encryption Keys and Hardware Root of Trust
Protecting Data with Short-Lived Encryption Keys and Hardware Root of Trust Speaker: Dan Griffin - President, JW Secure, Inc. The US National Security Agency...

By: TalksDump

Read the original here:
[DEFCON 21] Protecting Data with Short-Lived Encryption Keys and Hardware Root of Trust - Video

[DEFCON 21] A Password is Not Enough: Why disk encryption is broken and how we might fix it – Video


[DEFCON 21] A Password is Not Enough: Why disk encryption is broken and how we might fix it
A Password is Not Enough: Why disk encryption is broken and how we might fix it Speaker: Daniel Selifonov Since the publication of the cold boot attack on so...

By: TalksDump

Read more here:
[DEFCON 21] A Password is Not Enough: Why disk encryption is broken and how we might fix it - Video

How to Backup Pictures and Files with Password Encryption on the Internet – Video


How to Backup Pictures and Files with Password Encryption on the Internet
On this video you will see that my files are stored in a Network Attach Storage (NAS). It will be automatically backup by a freeware software to a specific l...

By: widewings007

Go here to read the rest:
How to Backup Pictures and Files with Password Encryption on the Internet - Video

Backup your Recovery Key for BitLocker® encryption for a Drive/Partition In Windows® 8.1 – Video


Backup your Recovery Key for BitLocker encryption for a Drive/Partition In Windows 8.1
BitLocker recovery key can be used to gain access to your PC if the drive is encrypted with BitLocker. To create a backup of the recovery key for BitLocker...

By: iYogi

Continue reading here:
Backup your Recovery Key for BitLocker® encryption for a Drive/Partition In Windows® 8.1 - Video

Apple encryption mistake puts many desktop applications at risk

A subtle mistake in how Apple implemented a basic encryption feature that shields data from snooping also affects many desktop applications that rely on the code, according to a noted security researcher.

Apple released a patch on Friday for its iOS mobile platform but has yet to fix the problem for desktop computers, which often have several applications that rely on the faulty code library, called Secure Transport.

Ashkan Soltani, an independent privacy and security researcher, said many other Apple and non-Apple applications are affected.

Security researcher Ashkan Soltani said several other desktop applications, include Apples Mail, FaceTime and Calendar, use a code library that could allow an attacker to steal data. (Click to enlarge.)

Those include Apples Mail, FaceTime, Calendar, Keynote, the Safari browser, iBooks and its Software Update applications. It would also appear to affect third-party applications, such as the desktop Twitter application and possibly VPN (virtual private network) connections, depending on their configurations, Soltani said.

The Secure Transport library, which handles setting up an encrypted connection for many applications, was contained in iOS 6 and up and OSX versions 10.9 and up, Soltani said via email.

Most websites handling sensitive personal data use SSL (Secure Sockets Layer) or TLS (Transport Layer Security), which establishes an encrypted connection between a server and a persons computer. If an attacker intercepts the data, it is unreadable.

Apples mistake in Secure Transport allows an attacker to perform a man-in-middle attack, and supply fake data that makes it appear an authentic web service has been cryptographically verified.

This enables an adversary to masquerade as coming from a trusted remote endpoint, such as your favorite webmail provider and perform full interception of encrypted traffic between you and the destination server, wrote Alex Radocea, senior engineer with the computer security firm CrowdStrike, on Friday. CrowdStrike analyzed Apples patch for iOS after it was released.

The flaw is deeply buried in a line of code, wrote Adam Langley, a software engineer at Google, on his personal blog.

More:
Apple encryption mistake puts many desktop applications at risk