Paul Smith A/W 05 Collection (Men)








18 of 43 AW 05 Collection Pale pink mohair knit, brown gingham shirt and purple check trousers.





















19 of 43 AW 05 Collection Pink mohair knit, purple gingham shirt and check trousers.





















33 of 43 AW 05 Collection Pink Afghan intarsia knit, green garland print shirt and charcoal check trousers.












As usual...I am not affiliated to Paul Smith in any way ...I am not promoting Paul Smith products. All the above collections belongs to the Paul Smith fashion house. I am just another one of their happy customers.... :)

Paul Smith A/W 05 Collection (Women)







9 of 40 AW 05 Collection Black leather A line button skirt, cream cable knit double breasted short cape, purple cashmere polo neck, orange tights, black patent low heeled shoes.



















31 of 40 AW 05 Collection Brown leather python jeans, fruity floral printed jersey shirt, white vest, purple socks, black patent low heeled shoes, dark brown studded belt, green leather gloves.



















37 of 40 AW 05 Collection Blue and black skinny jeans, tonic two button suit jacket, plum spotted shirt, black silk spotted scarf, brown leather belt with eyelets, fuschia tartan patent low heeled shoes.













As usual...I am not affiliated to Paul Smith in any way ...I am not promoting Paul Smith products. All the above collections belongs to the Paul Smith fashion house. I am just another one of their happy customers.... :)

Join the industries leading IT Security Managers for this strategic summit

With each passing year information security becomes a greater challenge for credit unions. Whether its hype or reality one thing is for certain: The threats continue to evolve, making risk management an increasingly difficult and time consuming task. Patch management, email security, and incident response are a constant challenge. Phishing attacks have hit the industry with a vengeance and we are now looking for new ways to address authentication and member awareness. Even the regulators are now modifying their expectations. Information security is no longer a task to be resolved by the IT department alone.

The face of security is changing! How do you determine what the most critical issues are? How do you gain the support you need? What are the most efficient and affordable ways to manage these risks? CUISPA2006 will bring credit union IT Information Security leaders together for a three day strategic summit to discuss the hottest issues relating to security and risk management.

As the first national Risk Management Summit organized specifically for CU personnel, CUISPA2006 will deliver insight, ideas and answers. Each session will host an interactive presentation designed to encourage input and shed light on the strategies, practices, and available solutions that others have found successful. CUISPA2006 is about sharing knowledge. It's about cooperation.

• IT Risk Management
• Security Assessment
• Encryption
• Secure Member Communication
• Disaster Recovery
• Log Management and Monitoring
• ID Theft Prevention
• Controlling Malware
• Biometrics
• 2-factor Authentication
• Regulatory Compliance

CUISPA 2006

Bank of America's move to stronger authentication delayed

But it still plans to roll out SiteKey for all 14.3M customers by early next year

News Story by Robert McMillan

OCTOBER 21, 2005 (IDG NEWS SERVICE) - Bank of America Corp.'s rollout of a stronger user authentication technology has hit a snag and is now expected to be completed in the early part of 2006, several months later than originally planned.

The Charlotte, N.C.-based bank had expected to make the new authentication service, called SiteKey, mandatory for all of the bank's 14.3 million online banking customers sometime this month, according to Betty Riess, a spokeswoman for Bank of America. "We've made some adjustments in terms of the rollout schedule."

She declined to comment on what caused the delay, saying only that "sometimes when you get to actually doing the implementation, you make adjustments."

Still, a large number of Bank of America U.S. customers are already using SiteKey. The system is in place in the Southeast, Midwest and Southwest, and is expected to be in use in California, the Northeast and the Northwest by year's end, Riess said. Most customers will be forced to adopt the system by year's end, with the final two states -- Washington and Idaho -- going online early next year.

Based on software developed by Menlo Park, Calif.-based PassMark Security Inc., SiteKey is able to recognize when a Bank of America account is being accessed via an unknown computer. It can then generate a predetermined "challenge" question, adding another level of security to the process of logging in. The software also lets users choose a specific image -- a photograph of a dog, for example -- that can then be reshown to users in order to reassure them that they are actually visiting the Bank of America Web site and not some other site masquerading as www.bofa.com.
The SiteKey rollout may put Bank of America ahead of the curve on new federal regulations, which are due to take effect next year (see "Banks get new online authentication guidelines").

Last week, the Federal Financial Institutions Examination Council released guidelines calling for U.S. banks to use a stronger form of authentication than the username and password logins typically used in online banking today. The guidelines call for Internet bankers to add a new form of authentication to their online banking systems by the end of 2006. They do not spell out which techniques to use, leaving banks some leeway to develop their own approaches to stronger authentication.

Though Riess declined to comment on whether or not Bank of America's system meets these requirements, PassMark believes that its software qualifies, according to Mark Goines, PassMark's chief marketing officer.

In addition to Bank of America, PassMark's software is being used by Stanford Federal Credit Union in Palo Alto, Calif., Goines said. Online brokerage Scottrade Inc. is also rolling out the software, he said.

Cyber eye: And the worst security idea of 2005 was . . .

By William Jackson
Goverment Computer News Staff

Tis the season for looking back and recognizing landmark accomplishments of the past year. Any number of awards for IT achievement are being handed out, but we shouldn’t ignore failures. After all, we learn from our mistakes.

So the first Bonehead Award for Notable Failures in IT Security goes to the 360 senators and congressmen who voted for the Real ID Act of 2005, and to the president who signed it into law.

The Real ID Act, now a part of Public Law 109-13, may not be the worst piece of legislation passed during the year, but it certainly is a model for how not to do information security.

I’m talking specifically about the part of the act establishing minimum requirements for state-issued driver’s licenses and ID cards, which falls prey to one of the most dangerous IT errors: designing a system to handle sensitive information without considering security requirements.

Under the law, the new cards must contain, in machine-readable format (read: digital), the holder’s name, date of birth, address, ID number, signature and photo. The act not only fails to require any encryption or other security for data stored on the cards, but also mandates the creation of shared state databases of sensitive information with no security or access restrictions.

This is particularly disturbing given the type and amount of data the act requires states to gather on citizens. States must “capture digital images of identity source documents so that the images can be maintained in electronic storage in transferable format” for 10 years. Each state must provide all other states electronic access to this data.

The ability of any Tom, Dick or Harry with a card reader to capture a copy of your vital statistics from your driver’s license is worrisome. The creation of unsecured databases containing digital images of your birth certificate and other documents is even more so.

Under the terms of this act, every bartender, bank teller or cop who swipes your electronic card is free to do as he or she pleases with the information that is captured. States are free to sell their databases to anyone for any reason, and even to access other states’ databases and sell that data.

Given that Congress now is considering legislation that would require companies to tighten security on personal data, it is particularly boneheaded to ignore this issue in government databases.

Congress no doubt will say it is up to states to determine the proper security measures and access controls for this data; but that is wrong. If the federal government mandates collection of personal data, the proper place for security requirements on that data is in the federal law.

Making the problem worse

With the glut of personal information already being exposed through the actions of hackers, thieves and entrepreneurs, you could argue that it is too late to worry about the privacy of data held by the government. But even if we cannot expect the government to completely solve the problems of identity theft and invasion of privacy, the least we can ask for is that government not make the problems worse.

But apparently that’s more than we can hope for.

William Jackson is a GCN senior writer. E-mail him at wjackson@postnewsweektech.com.

This article is the work of William Jackson and it either belongs to him or GCN. I solely put this article here for the purpose of spreading knowledge & coz I think it is interesting.