How do I responsibly dispose of backup tapes?

Our old tape drives have failed and we not using tapes for backup anymore. We still have a stack of DLT tapes with backups which may contain sensitive information like credit card numbers, social security numbers, etc.

How do I responsibly dispose of these backup tapes?

If I had a working drive I would be tempted to dd from /dev/urandom to the tape device, but the drives have failed. Would this be a good method if the drive was still working? What do you recommend I do with these tapes given that I have no working drive for them?

Related:

Single sign on to a IBM WebSphere Portal through IBM Tivoli Access Manager WebSEAL

Your article abstract goes here. Put the main points and key phrases at the beginning of the abstract, because it may be truncated in search results. Make
your abstract enticing yet succinct. Aim for three to five sentences that express
why the reader would care about the content (motive) and what he or she can
gain from reading the content (benefits).

Related:

  • No Related Posts

Understanding single sign-on (SSO) between IBM Lotus Domino and IBM WebSphere Portal

This white paper provides an in-depth explanation of how the single
sign-on (SSO) feature works between IBM Lotus Domino and IBM WebSphere Portal.
Learn the basics of how cookies are written to―and used in―Internet browsers,
how the cookies are used to enable SSO, and exactly what is in the token and
why it’s needed for SSO between two servers. Included are specific details of
where the WebSphere Portal and Lotus Domino servers configure each part of the
cookie used for SSO, the LTPAToken. Editor’s Note: This white paper is the
first in a three-part series on SSO to be published over the next few months.
See the second paper, “Configuring single sign-on (SSO) between IBM WebSphere
Portal and IBM Lotus Domino.”

Related:

  • No Related Posts

User Centric Identity with Tivoli Federated Identity Manager, Part 2: Self registration and account recovery using information cards and OpenID

Attracting users to register at your retail Web site has always been a challenge. Not only do you need to have a fantastic service to offer, you also need to make the on-boarding process as simple and convenient as possible.
Traditional federation technologies like Liberty and SAML allowed companies to collaborate with tightly-coupled user bases by establishing 1:1 or many:few relationships; however, that model does not scale to the true retail space.
User Centric Identity management technologies like OpenID and Information Cards allow people to manage their own identity attributes at distributed “Identity Providers” (including self-issued Information Cards).
This article will demonstrate how to implement self-registration using an Information Card or OpenID (with the simple registration extension – SREG). Automated recovery of an account is also implemented, such as when
the user centric credential with which it was registered is lost. Sample code is provided to rapidly enable these capabilities with IBM Tivoli Federated Identity Manager 6.2.

Related:

  • No Related Posts

Managing OpenID trusted sites with Tivoli Federated Identity Manager

IBM Tivoli Federated Identity Manager 6.2 (TFIM) introduces support for OpenID 1.1 and 2.0 authentication protocols. When configured in the role of an OpenID Provider (Identity Provider), TFIM allows end users to record choices about authenticating to trusted relying-party sites. For example a user may select “Allow authentication forever” to a particular relying-party, and may select which attributes they are willing to share with that site. By default TFIM stores these choices in persistent cookies on the user’s browser. The cookie technique is effective, but not portable for users across different browsers. This article will demonstrate how to write your own plug-in for the storage and retrieval of user choices (for example to a database) via the TFIM TrustedSitesManager extension point.

Related:

  • No Related Posts

Secure replication in IBM Tivoli Directory Server

The article describes how to easily configure different replication topologies in IBM Tivoli Directory Server (TDS) using simple shell scripts. These scripts can be used to configure all known replication topologies (like Peer-peer, Master-Replica-Forwarder, Gateways etc) using simple bind, SSL with certificates or Kerberos authentication mechanism. The information in this article applies to TDS version 5.2 and later.

Related:

  • No Related Posts

Tivoli Directory Server 6.1 password policy : enhancements, configuration and troubleshooting

A password policy is a set of rules designed to enhance security by encouraging users to employ strong passwords and use them properly. A password policy is often part of an organization’s official regulations which ensures that users change their passwords periodically, passwords meet construction requirements, the re-use of old password is restricted, and users are locked out after a certain number of failed attempts. This article is intended to highlight the new features introduced with IBM Tivoli Directory Server(TDS) 6.1 release and describe the ways of debugging trivial password policy problems in TDS.

Related:

  • No Related Posts

Understanding the Tivoli Federated Identity Manager Information Service 6.2

IBM Tivoli Federated Identity Manager 6.2 (TFIM) provides a Web service
interface designed to obtain federation, federated user, and user alias
information from a TFIM environment. This Web service is known
as the TFIM Information Service. This article shows how to create a Web service
client from the interface using Rational Application Developer 7.0
and also contains a sample application which uses the newly created
Web service client to query federation, federated user and user alias information.

Related:

  • No Related Posts