SIMalliance has published an illustration intended to help NFC service providers to understand the cost considerations of different NFC deployment models. The illustration compares the known and hidden conceptual costs of deploying NFC services via three deployment technologies: UICC (secure element), Embedded Secure Element (eSE) and Host Card Emulation (HCE). Within the visual, SIMalliance also evaluates the ‘risk of attack’ associated with each model and suggests that this is also a cost that service providers need to consider.
This Easy Reference Guide introduces the Open Mobile API, which standardises the means of connecting mobile applications to the Secure Element within mobile devices, and clearly lays out the benefits of using OMAPI to OEMs.
This Easy Reference Guide introduces the Open Mobile API, which standardises the means of connecting mobile applications to the Secure Element within mobile devices, and clearly lays out the benefits of using OMAPI to developers.
With the explosion of the mobile applications market, there is an unprecedented need to secure many different types of mobile service. This infographic offers an overview of the OMAPI specification and how it is being used, in conjunction with the secure element, to secure these services.
In an interview with Jane Cooper, Technology Editor at The Banker, SIMalliance Chairman Hervé Pierre discusses how near-field communication (NFC) is evolving and what banks need to consider when implementing an NFC programme.
This paper provides an introduction to Android’s Host Card Emulation (HCE) and explores its value to the NFC ecosystem relative to the Secure Element (SE). SIMalliance contends that while HCE is good for the NFC ecosystem as a whole (increasing end-user familiarity with NFC through additional services, driving adoption and encouraging new developers into the ecosystem), the technology remains immature, un-standardised and, relative to SE-based deployments, vulnerable to malicious attack.
This paper gives an introduction to the importance of Secure Elements (SE) in M2M deployments, provides an overview of the market and addresses the benefits of embedded SE technology in an M2M context.
In the world before the app store, delivering an application to millions of subscribers was a long, complex process. That all changed with the appearance of the application store marketplaces. In this webinar, Michele Scarlatella, Board Director, SIMalliance, discusses the security implications of this rapidly evolving environment for application development and delivery.
While the sources vary, the message is clear; attacks on mobile internet devices and connected smartphones are increasing rapidly. In this paper we look in detail at the issue of mobile internet security, analyze existing authentication methods, and ask whether it is time for the widespread adoption of the Secure Element by the mobile community.
This paper highlights the need for a change in how security is approached on the connected mobile device. It focuses on the need to create security (and security policy) at the development stage, and highlights the telecoms industry’s unique position of already having a solution to the problem. It discusses why ‘buy in’ is needed from the application development and operating systems communities, and introduces the SIMalliance’s new Open Mobile API workgroup whose task it is to connect the application, operating system and the operator with the Secure Element found in billions of connected devices right across the world.
Released on 27.09.2015
This License Agreement (Agreement) is a legal agreement between you and SIMalliance. (Licensor), which is the owner of the specification (Specification) you will be downloading when you complete this Agreement. As used in this Agreement, "you" means the company, entity or individual that is acquiring a license under this Agreement.
By clicking on the "ACCEPT" button below, you are agreeing that you will be bound by and are becoming a party to this Agreement. If you are an entity, and an individual is entering into this Agreement on your behalf, then you will be bound by this Agreement when that individual clicks on the "ACCEPT" button. When they do so, it will also constitute a representation by the individual that s/he is authorized to bind you as a party to this Agreement. If you do not agree to all of the terms of this Agreement, click the "DO NOT ACCEPT" button at the end of this Agreement.
1. License Grant.
Licensor hereby grants you the right, without charge, on a perpetual, non- exclusive and worldwide basis, the right to utilize the Specification for the purpose of developing, making, having made, using, marketing, importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complying with the Specification, in all cases subject to the conditions set forth in this Agreement and any relevant patent and other intellectual property rights of third parties (which may include members of Licensor). This license grant does not include the right to sublicense, modify or create derivative works based upon the Specification. For the avoidance of doubt, products implementing this Specification are not deemed to be derivative works of the Specification.
2. NO WARRANTIES.
THE SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, COMPLETENESS AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL LICENSOR, ITS MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SPECIFICATION.
3. THIRD PARTY RIGHTS.
Without limiting the generality of Section 2 above, LICENSOR ASSUMES NO RESPONSIBILITY TO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT, OR IN ANY FUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION, LICENSOR TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.
4. TERMINATION OF LICENSE.
In the event of a breach of this Agreement by you or any of your employees or members, Licensor shall give you written notice and an opportunity to cure. If the breach is not cured within thirty (30) days after written notice, or if the breach is of a nature that cannot be cured, then Licensor may immediately or thereafter terminate the licenses granted in this Agreement.
All notices required under this Agreement shall be in writing, and shall be deemed effective five days from deposit in the mails. Notices and correspondence to either party shall be sent to its address as it appears below. This Agreement shall be construed and interpreted under the internal laws of the United Kingdom, without giving effect to its principles of conflict of law.