Risk
1/7/2014
02:32 PM
Dark Reading
Dark Reading
Products and Releases
Connect Directly
RSS
E-Mail
50%
50%

Hoyos Labs Issues Biometric Open Protocol Standard For Safer Authentication

BOPS comprises a set of rules that govern secure communications among a variety of client devices

LAS VEGAS, Jan. 7, 2014 /PRNewswire/ -- from ShowStoppers @ CES 2014 -- While biometrics are becoming a ubiquitous component of securing consumer data on mobile and other digital devices, there is no industry standard in place to protect that data once it leaves the device and enters the cloud. Today, Hoyos Labs, a leading digital infrastructure company, announced the formalization of its Biometric Open Standards Protocols (BOPS).

BOPS comprises a set of rules that govern secure communications among a variety of client devices including mobile phones, desktop computers and ATMs, among others, and a trusted server managing the acquisition and manipulation of biometric data captured by those devices. The BOPS guidelines make use of The U.S. Department of Defense's Trusted Computer Systems Evaluation Criteria (TCSEC) and are biometric agnostic.

"Nearly every smartphone, digital device or computer system that has a financial component to it will have a biometric component built into it in the very near future. The concerns about fraud, hacking and personal privacy have created a tidal wave of momentum on this front," said Hector Hoyos, founder and Chief Executive Officer of Hoyos Labs. "Now, securing all of the biometric data that's being generated is of the utmost importance. As with every major technological breakthrough, a series of accepted standards and protocols must be widely adopted from the manufacturer and database management end before consumers can fully be comfortable. BOPS are those standards and protocols."

Hoyos continued, "We have created a rule-based system by building upon The U.S. Department of Defense's core infrastructures. What Hoyos Labs has done is made our system work across all biometric types - from iris and periocular to fingerprint and beyond - and is available to any company that wants to implement it."

The BOPS system addresses the five most widely recognized key security consideration components:

-- Identity Assertion - The BOPS identity assertion platform provides a guarantee that named users are who they claim to be. The identity assertion implies reliance on human biometrics; however, the BOPS is an interoperable standard and can incorporate any identity asserter, or a number of asserters, that provides this guarantee. The application of the Intrusion Detection System (IDS) provides active monitoring to prevent spoofing of the credentials set and blacklisting of a subject or device that makes malicious attempts. -- Role Gathering - Role gathering is focused on the data confidentiality and privileged access based on the rules enforced by a known system. To determine whether a specific access mode is allowed, the privilege of a role is compared to the classification of the group to determine if the subject is authorized for a confidential access. The objects structure is defined by the access control. Role gathering occurs on the system's level or through the client/server call. The BOPS server stores role-gathering information to associate a unique user with a unique device. -- Access Control - The BOPS supports access control between the named users and the named objects (e.g., files and programs). The adjudication mechanism is role-based and allows users and administrators to specify and control the sharing of those objects by named individuals, or defined groups of individuals, or by both. -- Auditing - The BOPS supports all auditing requests at the subject/object level or at the group level. The BOPS uses Aspect Oriented Programming (AOP) to ensure that all calls are safely written to an audit trail. A RESTFul web services and JSON interface provides a mechanism to read the audit trail. Auditing may occur at the subject per action, the object per action or the group per action. For example, a group of users called "Accounting" may audit all writes to General Ledger. Or the "Chief Financial Officer" may have audits for reads of the Income Statement. -- Assurance - The auditing of all BOPS specifications and proof of the security model to prevent a system from unknowingly being compromised. The entire BOPS document is available upon request from Hoyos Labs at no cost, with a properly executed non-disclosure agreement between the party who is requesting it and Hoyos Labs. Please contact: hoyos@kcsa.com.

About Hoyos Labs Hoyos Labs is a digital infrastructure security company with security, computer vision and biometrics and big data experts. The goal of Hoyos Labs is to develop and deploy enterprise and consumer identity assertion technology platforms that will conveniently and securely address the identity assertion challenges of today. Hoyos Labs currently has offices in New York, Boston, Bucharest (Romania) and Beijing (China).

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3541
Published: 2014-07-29
The Repositories component in Moodle through 2.3.11, 2.4.x before 2.4.11, 2.5.x before 2.5.7, 2.6.x before 2.6.4, and 2.7.x before 2.7.1 allows remote attackers to conduct PHP object injection attacks and execute arbitrary code via serialized data associated with an add-on.

CVE-2014-3542
Published: 2014-07-29
mod/lti/service.php in Moodle through 2.3.11, 2.4.x before 2.4.11, 2.5.x before 2.5.7, 2.6.x before 2.6.4, and 2.7.x before 2.7.1 allows remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) is...

Best of the Web
Dark Reading Radio