Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
Processing registration... Please wait.
This process can take up to a minute to complete.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
The Payment Card Industry Security Standards Council (PCI SSC), an industry body which manages payment data security guidelines, released best practices for mobile app developers and device manufacturers.
The main focus of the guidelines is to provide direction on securing mobile device payment processes, as well as the payment environment itself, by educating developers in the emerging mobile app market.
Bob Russo, the general manager of the PCI SSC, told SC the guidelines are particularly relevant today.
“I tell people that convenience trumps security all the time, and people are running quickly to use these new devices and technology, without even thinking about security,” Russo said. “This guidance is actually for the developers of those devices. We are purposely being cautious. It's such a changing market – you'll put something out today and tomorrow people are using it.”
Mobile devices have become payment vehicles and, accordingly, warrant strategies for security, he added.
Key recommendations of the report include isolating sensitive functions and data in trusted environments, implementing secure coding best practices and eliminating unnecessary third-party access and privilege escalation. Developing ways to remotely disable payment functions, in addition to creating tools for mobile apps to monitor and report suspicious activity were also among the recommendations.
The guidelines focus on ways to prevent account data from being intercepted while sent or received on mobile devices or from being compromised while being processed or stored on them.
Troy Leach, the chief technology officer of the council, told SCMagazine.com on Friday that the most recent guidelines reinforce the council's standard payment security goals, while applying them to a mobile space.
“We have a brand new group of developers that aren't of aware of their responsibility,” Leach said. “They are designing good code, but don't know all it's being used for.”
Malware, rootkits used by criminals and jailbreaking vulnerabilities are just some of the threats that can comprise the security of payments transmitted through mobile devices and apps.
David Thiel, the vice president for iSEC Partners, which provides mobile security consulting, told SCMagazine.com on Friday that a common problem in mobile app security is personal data being unintentionally leaked to local storage on devices, which can then be retrieved by attackers using malicious software on jailbroken phones.
“It's still a relatively immature field in terms of security development best practices, so its not quite to the level that a lot of big name software packages have been,” Thiel said of the app development market.
PCI SSC also recently announced a new qualification program, called the PCI Professional (PCIP) Program, for IT professionals to receive certification for PCI payment security standards.
This article originally appeared at scmagazineus.com
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.