Face Software is sometimes distributed under different names, such as 'Face Software versie', 'Face Software versione'. FaceSoft.exe is the most common filename for this program's installer. This PC program is compatible with Windows XP/Vista/7/8/10 environment, 32-bit version. The software is included in Home & Hobby Tools.
![]() -->
Microsoft face authentication in Windows 10 is an enterprise-grade identity verification mechanism that's integrated into the Windows Biometric Framework (WBF) as a core Microsoft Windows component called Windows Hello. Windows Hello face authentication utilizes a camera specially configured for near infrared (IR) imaging to authenticate and unlock Windows devices as well as unlock your Microsoft Passport.
Key benefits and capabilities of Windows Hello face authentication
These are the key benefits to using the Windows Hello face authentication:
Scenarios
The two primary scenarios for Windows Hello face authentication in Windows 10 are authentication to log on or unlock, and re-authentication to prove you are still there.
Authentication
Re-authentication
How it works
The Windows Hello face recognition engine consists of four distinct steps that allow Windows to understand who is in front of the sensor:
Enrollment
Enrollment is the step of generating a representation or set of representations of yourself (for example if you have glasses you may need to enroll with them and without them) and storing them in the system for future comparison. This collection of representations is called your enrollment profile. Microsoft never stores an actual image and your enrollment data is never sent to websites or applications for authentication.
From a security and data integrity perspective, Microsoft believes enrollment needs to be its own distinct step to ensure it is only ever you in front of the sensor. Windows will never automatically update your enrollment information – you are always in control. This helps ensure that your profile is not impacted by people nearby or by any other mechanism that might compromise robustness and security. Your profile can be manually updated, reset, or removed any time you choose.
Most users will likely need to enroll once per device. Additional enrollments are needed for users that:
Benefits of near infrared
After the release of face recognition with the first Kinect on Xbox 360, Microsoft learned that relying on ambient light to provide a consistent image provided a poor user experience. People live and work in a variety of environments, with an assortment of lighting conditions. Traditional color recognition systems rely on turning up the brightness, exposure, or other settings to create a useable image – all of which expose artifacts that impact the robustness of the system.
In contrast, near infrared images are consistent across ambient lighting scenarios, as you can see below.
Using IR also helps with spoofing because it helps prevent the most accessible attacks. For instance, IR doesn't display in photos because it's a different wavelength, and as you can see below, the images the images do not display in photos or on an LCD display.
How accuracy is measured
When Microsoft talks about the accuracy of Windows Hello face authentication, there are three primary measures used: False Positives, True Positives, and False Negatives.
Accounting for errors in measurement is important, so Microsoft categorizes them in two ways: bias errors (systematic errors) and random errors (sampling).
Bias errors![]()
Bias errors may occur as a result of not using data that is representative of the environments and the conditions in which the algorithm is used. This type of error can result from different environmental conditions (such as lighting, angle to sensor, distance, and so on) as well as hardware that is not representative if shipping devices.
Random errors
Random errors results from using data that doesn’t match the population diversity that will actually be using the feature. For example, focusing on a small set of faces without glasses, beards, or unique facial features.
Related topics
The Open GroupFuture Airborne Capability Environment (FACE Consortium) was formed in 2010 to define an open avionics environment for all military airborne platform types. Today, it is a real-time software-focused professional group made up of industry suppliers, customers, academia, and users. The FACE approach is a government-industry software standard and business strategy for acquisition of affordable software systems that promotes innovation and rapid integration of portable capabilities across programs. The FACE Consortium provides a vendor-neutral forum for industry and government to work together to develop and consolidate the open standards, best practices, guidance documents, and business strategy necessary to result in:[1]
The FACE Technical Standard is an open real-time standard for making safety-critical computing operations more robust, interoperable, portable and secure. Although the consortium started with a focus on avionics, the applicability of the technical standard and its associated data model have become much broader. The standard enables software developers to create and deploy a wide catalog of applications for use across the entire spectrum of real-time systems through a common operating environment. The latest edition of the standard further promotes application interoperability and portability with enhanced requirements for exchanging data among FACE components, including a formally specified data model, and emphasis on defining common language requirements for the standard.
Background[edit]
The FACE effort sprang from US Navy open architecture programs,[2] promoted by the US Naval Air Systems Command (NAVAIR), to enhance interoperability and software portability for avionics software applications across DoD aviation platforms. Both the US Army and US Air Force have been participating in the consortium. NAVAIR led the pack with early acquisitions, followed later by Army and Air Force.[3][4][5]
The FACE Consortium was formed by The Open Group as a 'Voluntary Consensus Standards Body', as defined by the National Technology Transfer Act and OMB Circular A-119. This facilitates government participation in the consortium.[6] One goal of the effort is to reduce the typical development and deployment cycle of new capabilities in military airborne platforms from as long as six years under the current methodology to as little as six months.[7]
The FACE reference architecture ecosystem includes software product conformance verification and certification processes.[8] In October 2016, a suite of flight management software earned the first FACE certificate of conformance.[9] One may view information on all certified FACE conformant products at the FACE Registry
Technical approach[edit]
The FACE technical approach tackles barriers to software modularity, portability, and interoperability by defining a Reference Architecture and employing design principles to enhance software portability. To meet the objectives of the technical approach, the FACE Technical Standard uses a standardized architecture describing a conceptual breakdown of functionality, called the FACE Reference Architecture, to promote the reuse of software components able to share common functionality across disparate systems. This architecture defines standardized interfaces to allow software components to be moved between systems, including those developed by different vendors. The standardized interfaces follow a data architecture to ensure the data communicated between the software components is fully described to facilitate their integration on new systems.
FACE Reference Architecture
The FACE Reference Architecture is composed of logical segments where variance occurs. The structure created by connecting these segments together is the foundation of the FACE Reference Architecture. The five (5) segments of the FACE Reference Architecture are the Operating System Segment (OSS), Input/Output Services Segment (IOSS), Platform-Specific Services Segment (PSSS), Transport Services Segment (TSS), and Portable Components Segment (PCS).
The FACE Reference Architecture defines a set of standardized interfaces providing connections between the FACE architectural segments. The standardized interfaces within the FACE Reference Architecture are the Operating System Segment Interface (OSS Interface), the Input/Output Services Interface (IOS Interface), the Transport Services Interfaces, and Component-Oriented Support Interfaces.
The FACE Reference Architecture defines three FACE OSS Profiles tailoring the Operating System (OS) Application Programming Interfaces (APIs), programming languages, programming language features, run-times, frameworks, and graphics capabilities to meet the requirements of software components for differing levels of criticality. The three Profiles are Security, Safety, and General Purpose. The Security Profile constrains the OS APIs to a minimal useful set allowing assessment for high-assurance security functions executing as a single process. The Safety Profile is less restrictive than the Security Profile and constrains the OS APIs to those that have a safety certification pedigree. The General Purpose Profile is the least constrained profile and supports OS APIs meeting real-time deterministic or non-real-time, non-deterministic requirements depending on the system or subsystem implementation.
The FACE Data Architecture defines the FACE Data Model Language (including the language binding specification), Query and Template language, FACE Shared Data Model (SDM) and the rules of construction of the Unit of Portability (UoP) Supplied Model (USM). Each PCS Unit of Conformance (UoC), PSSS UoC, or TSS UoC providing using TS Interfaces is accompanied by a USM consistent with the FACE SDM and defines its interfaces in terms of the FACE Data Model Language. A Domain-Specific Data Model (DSDM) captures content relevant to a domain of interest and can be used as a basis for USMs.
References[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Future_Airborne_Capability_Environment&oldid=902074989'
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |