DataPower and the PCI DSS (Data Security Standard)

DataPower ideal solution for many requirements:

•Build and Maintain a Secure Network
Requirement 1: Install and maintain a firewall configuration to protect cardholder data
–Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters
•Protect Cardholder Data
–Requirement 3: Protect stored cardholder data
–Requirement 4: Encrypt transmission of cardholder data across open, public networks
•Maintain a Vulnerability Management Program
–Requirement 5: Use and regularly update anti-virus software
–Requirement 6: Develop and maintain secure systems and applications
•Implement Strong Access Control Measures
–Requirement 7: Restrict access to cardholder data by business need-to-know
–Requirement 8: Assign a unique ID to each person with computer access
–Requirement 9: Restrict physical access to cardholder data
•Regularly Monitor and Test Networks
–Requirement 10: Track and monitor all access to network resources and cardholder data
–Requirement 11: Regularly test security systems and processes
•Maintain an Information Security Policy
–Requirement 12: Maintain a policy that addresses information security

Red – Complete Solution with Datapower
Blue – Partial Solution with Datapower

Types of Websphere MQ queues

Local queue object
A local queue object identifies a local queue belonging to the queue manager to which the application is connected. All queues are local queues in the sense that each queue belongs to a queue manager and, for that queue manager, the queue is a local queue.
Remote queue object
A remote queue object identifies a queue belonging to another queue manager. This queue must be defined as a local queue to that queue manager. The information you specify when you define a remote queue object allows the local queue manager to find the remote queue manager, so that any messages destined for the remote queue go to the correct queue manager.Before applications can send messages to a queue on another queue manager, you must have defined a transmission queue and channels between the queue managers, unless you have grouped one or more queue managers together into a cluster. For more information about clusters, see Remote administration using clusters

Alias queue object
An alias queue allows applications to access a queue by referring to it indirectly in MQI calls. When an alias queue name is used in an MQI call, the name is resolved to the name of either a local or a remote queue at run time. This allows you to change the queues that applications use without changing the application in any way; you merely change the alias queue definition to reflect the name of the new queue to which the alias resolves.An alias queue is not a queue, but an object that you can use to access another queue. 

Model queue object
A model queue defines a set of queue attributes that are used as a template for creating a dynamic queue. Dynamic queues are created by the queue manager when an application issues an MQOPEN request specifying a queue name that is the name of a model queue. The dynamic queue that is created in this way is a local queue whose attributes are taken from the model queue definition. The dynamic queue name can be specified by the application, or the queue manager can generate the name and return it to the application.Dynamic queues defined in this way can be temporary queues, which do not survive product restarts, or permanent queues, which do. 

Websphere Subnet Calculator

The latest Websphere Subnet Calculator for all your networking queries when install Datapower or any network appliance is now as easy as entering the IP address of the device and receiving all the relevant information.

Download the latest Websphere Subnet Calculator: Websphere Subnet Calculator