Great tools and resources are available to help you write secure Ruby on Rails code. Kurt examines some tools and offers some tips.

XML security problems are numerous, but you can take steps to limit your exposure – or you can use a different standard.

We look at what makes a security issue critical and how upstream developers and vendors respond by examining three incidents: CVE-2013-0156, CVE-2013-0333, and rubygems.org. incident response handling.

What do all programs have in common? They store data at some point, usually in arrays – everything from commandline options to the input and output. But how is data actually stored by the program? Kurt explains.

Using personal, self-signed certificates and digital encryption.

Creating backups is one thing, making sure they’re secure is another. We offer some tips for ensuring the process is as painless as possible.

The auditd tool can provide system logging capabilities to satisfy even the most paranoid users.