DOCSLIB.ORG

Secure Messaging Extension User's Guide (Monk)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Secure Messaging Extension User's Guide (Monk) Secure Messaging Extension User’s Guide Release 5.0.5 for Schema Run-time Environment (SRE) Monk Version Copyright © 2005, 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. Version 20101007170207. Secure Messaging Extension User’s Guide 2 Contents Contents Chapter 1 Introduction 5 Overview 5 Intended Reader 5 Components 5 Introducing S/MIME 6 Introducing Secure Messaging Extension 7 Supported Operating Systems 10 System Requirements 10 Environment Variable Settings 10 Chapter 2 Installation 11 Windows 11 Pre-installation 11 Installation Procedure 11 UNIX 12 Pre-installation 12 Installation Procedure 12 Files/Directories Created by the Installation 13 Chapter 3 Implementation 14 Sample Configuration 14 Sample Implementation 15 Sample Monk Scripts 15 Certificate Formats 15 Secure Messaging Extension User’s Guide 3 Contents Chapter 4 Secure Messaging Extension Functions 19 Secure Messaging Extension Functions 19 begin-session 19 db-query 20 db-store 21 end-session 23 set-param 24 sign-encrypt 26 verify-decrypt 28 wipe-handle 30 Index 31 Secure Messaging Extension User’s Guide 4 Chapter 1 Introduction This document discusses how to install and configure Secure Messaging Extension. 1.1 Overview Secure Messaging Extension enables e*Gate to process Events utilizing the S/MIME (Secure Multipurpose Internet Mail Extensions) message format. Secure Messaging Extension supports encryption, decryption and authentication of messages and is interoperable with any other client applications that support the S/MIME standard. This adds the following features to a transaction: privacy message (Event) authentication sender authentication nonrepudiation. 1.1.1 Intended Reader The reader of this guide is presumed to be a developer or system administrator with responsibility for maintaining the e*Gate system; to have expert-level knowledge of Windows and/or UNIX operations and administration; and to be thoroughly familiar with Windows-style GUI operations. 1.1.2 Components The following components comprise Secure Messaging Extension: Secure Messaging Extension Monk function scripts Dynamically loaded libraries (DLLs) Monk collaborations that load and call their functions. A complete list of the installed files appears in Table 1 on page 13. Secure Messaging Extension User’s Guide 5 Chapter 1 Section 1.2 Introduction Introducing S/MIME 1.2 Introducing S/MIME Secure Multipurpose Internet Mail Extension (S/MIME) is a type of MIME message format that supports digital signatures and encryption of messages. The new form is based on the public-key encryption technology created by RSA Data Security, Inc. The RSA algorithm is based on the fact that there is no efficient way to factor very large numbers, making nearly it impossible to derive the private key based solely on the public key. The public-key encryption system uses two keys: a public key known to everyone and a private key known only to the recipient of the message. For example, if JaneDoe wants to send a secure message to JohnDoe, JaneDoe uses JohnDoe’s public key to encrypt the message. JohnDoe then utilizes his own private key to decrypt it. Only the public key can be used to encrypt messages, and only the corresponding private key can be used to decrypt them (and vice versa). Similarly, the sender utilizes his/her private key to include a signature on the message, while the recipient uses the sender’s public key to verify the signature. MIME offers a standardized way to represent and encode a wide variety of media types for transmission via the internet. Many e-Mail clients now support MIME, which enables sending and receiving of graphics, audio, and video files via the Internet. MIME also supports messages in character sets other than ASCII. When using MIME, messages can contain the following data types: Text messages in US-ASCII Character sets other than US-ASCII Multi-media: Image, Audio, and Video messages Multiple objects in a single message Messages of unlimited length Binary files. With the implementation of S/MIME, the protocol is available that adds digital signatures and encryption to these messages. These messages consist of two parts: the header and the body. The header forms a collection of field/value pairs structured to provide information necessary for the transmission of the message. MIME defines how the body of a message is structured. This format permits the inclusion of the above mentioned data types in a standardized manner. S/MIME defines the security services, adding digital signatures and encryption, thus preventing forgery and interception. For more information regarding S/MIMIE, please see RSA Laboratories’ Frequently Asked Questions About Today’s Cryptography, available online at: http://www.rsasecurity.com/rsalabs/faq/. Also available is Internet Engineering Task Force S/MIME Message Specification (proposed standard) at: http://www.ietf.org/rfc/rfc2633.txt. Secure Messaging Extension User’s Guide 6 Chapter 1 Section 1.3 Introduction Introducing Secure Messaging Extension 1.3 Introducing Secure Messaging Extension The Secure Messaging Extension provides security features, allowing the secure transmission of exchanges over public domains such as the Internet. Secure Messaging Extension adds the ability to use Public Key Infrastructure (PKI) technology to ensure the confidentiality of exchanges by digitally signing and encrypting messages as they are sent, and decrypting and authenticating messages when they are received. The Secure Messaging Extension performs the encryption and decryption of messages using the S/MIME standard. The standard one-way hash algorithms ensure data integrity by verifying that no modifications are made to the message while in transit. The identity of the sender of a message is verified through the use of digital signatures, proving that the message actually originated from the entity who claims to have sent it. The following flowcharts show the processing of the data from receipt to destination. Secure Messaging Extension User’s Guide 7 Chapter 1 Section 1.3 Introduction Introducing Secure Messaging Extension Figure 1 Inbound Signed/Encrypted Message Receives an Inbound Message No Encrypted Event? Yes Separate Block encrypted Event from PKI encrypted Session Key Encryption No required for this Event? Retrieve Receiver's Private Key from PKI Database
Load more

Recommended publications
  • Obstacles to the Adoption of Secure Communication Tools
    Obstacles to the Adoption of Secure Communication Tools Ruba Abu-Salma M. Angela Sasse Joseph Bonneau University College London, UK University College London, UK Stanford University & EFF, USA Anastasia Danilova Alena Naiakshina Matthew Smith University of Bonn, Germany University of Bonn, Germany University of Bonn, Germany Abstract—The computer security community has advocated Recent mobile phone-based secure communication tools widespread adoption of secure communication tools to counter have often been designed to hide security from the user com- mass surveillance. Several popular personal communication tools pletely (albeit at some security cost [1]). WhatsApp famously (e.g., WhatsApp, iMessage) have adopted end-to-end encryption, and many new tools (e.g., Signal, Telegram) have been launched deployed E2E encryption to approximately a billion users with security as a key selling point. However it remains unclear through a code update to its application for messages, voice if users understand what protection these tools offer, and if they calls and video communications [18], with only negligible value that protection. In this study, we interviewed 60 partici- changes to the user experience. Some other communication pants about their experience with different communication tools tools (e.g., Signal, Threema) have launched with security and their perceptions of the tools’ security properties. We found that the adoption of secure communication tools is hindered by as an explicit selling point, but they also hide nearly all fragmented user bases and incompatible tools. Furthermore, the cryptographic details. vast majority of participants did not understand the essential There are key differences in the security model of dif- concept of end-to-end encryption, limiting their motivation to ferent E2E-encrypted tools, in addition to a large gap in adopt secure tools.
    [Show full text]
  • Analysis and Implementation of the Messaging Layer Security Protocol
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by AMS Tesi di Laurea Alma Mater Studiorum · Universita` di Bologna CAMPUS DI CESENA Dipartimento di Informatica - Scienza e Ingegneria Corso di Laurea Magistrale in Ingegneria e Scienze Informatiche Analysis and Implementation of the Messaging Layer Security Protocol Tesi in Sicurezza delle Reti Relatore: Presentata da: Gabriele D'Angelo Nicola Giancecchi Anno Accademico 2018/2019 Parole chiave Network Security Messaging MLS Protocol Ratchet Trees \Oh me, oh vita! Domande come queste mi perseguitano. Infiniti cortei d'infedeli, citt`agremite di stolti, che v'`edi nuovo in tutto questo, oh me, oh vita! Risposta: Che tu sei qui, che la vita esiste e l’identit`a. Che il potente spettacolo continua, e che tu puoi contribuire con un verso." - Walt Whitman Alla mia famiglia. Introduzione L'utilizzo di servizi di messaggistica su smartphone `eincrementato in maniera considerevole negli ultimi anni, complice la sempre maggiore disponi- bilit`adi dispositivi mobile e l'evoluzione delle tecnologie di comunicazione via Internet, fattori che hanno di fatto soppiantato l'uso dei classici SMS. Tale incremento ha riguardato anche l'utilizzo in ambito business, un contesto dove `epi`ufrequente lo scambio di informazioni confidenziali e quindi la necessit`adi proteggere la comunicazione tra due o pi`upersone. Ci`onon solo per un punto di vista di sicurezza, ma anche di privacy personale. I maggiori player mondiali hanno risposto implementando misure di sicurezza all'interno dei propri servizi, quali ad esempio la crittografia end-to-end e regole sempre pi`ustringenti sul trattamento dei dati personali.
    [Show full text]
  • Introduction to Public Key Technology and Federal PKI Infrastructure
    Withdrawn NIST Technical Series Publication Warning Notice The attached publication has been withdrawn (archived), and is provided solely for historical purposes. It may have been superseded by another publication (indicated below). Withdrawn Publication Series/Number NIST Special Publication 800-32 Title Introduction to Public Key Technology and the Federal PKI Infrastructure Publication Date(s) February 26, 2001 Withdrawal Date September 13, 2021 Withdrawal Note SP 800-32 is withdrawn in its entirety. Superseding Publication(s) (if applicable) The attached publication has been superseded by the following publication(s): Series/Number Title Author(s) Publication Date(s) URL/DOI Additional Information (if applicable) Contact Computer Security Division (Information Technology Laboratory) Latest revision of the N/A attached publication Related Information https://csrc.nist.gov/projects/crypto-publication-review-project https://csrc.nist.gov/publications/detail/sp/800-32/archive/2001-02-26 Withdrawal https://csrc.nist.gov/news/2021/withdrawal-of-nist-special-pubs-800-15-25- Announcement Link and-32 Date updated: September 13, 2021 SP 800-32 IIInnntttrrroooddduuuccctttiiiooonnn tttooo PPPuuubbbllliiiccc KKKeeeyyy TTTeeeccchhhnnnooolllooogggyyy aaannnddd ttthhheee FFFeeedddeeerrraaalll PPPKKKIII IIInnnfffrrraaassstttrrruuuccctttuuurrreee D. Richard Kuhn Vincent C. Hu 26 February 2001 W. Timothy Polk Shu-Jen Chang 1 National Institute of Standards and Technology, 2001. U.S. Government publication. Not subject to copyright. Portions of this document have been abstracted from other U.S. Government publications, including: “Minimum Interoperability Specification for PKI Components (MISPC), Version 1” NIST SP 800-15, January 1998; “Certification Authority Systems”, OCC 99-20, Office of the Comptroller of the Currency, May 4, 1999; “Guideline for Implementing Cryptography in the Federal Government”, NIST SP800-21, November 1999; Advances and Remaining Challenges to Adoption of Public Key Infrastructure Technology, U.S.
    [Show full text]
  • Efail: Breaking S/MIME and Openpgp Email Encryption Using Exfiltration Channels
    Efail: Breaking S/MIME and OpenPGP Email Encryption using Exfiltration Channels Damian Poddebniak and Christian Dresen, Münster University of Applied Sciences; Jens Müller, Ruhr University Bochum; Fabian Ising and Sebastian Schinzel, Münster University of Applied Sciences; Simon Friedberger, NXP Semiconductors, Belgium; Juraj Somorovsky and Jörg Schwenk, Ruhr University Bochum https://www.usenix.org/conference/usenixsecurity18/presentation/poddebniak This paper is included in the Proceedings of the 27th USENIX Security Symposium. August 15–17, 2018 • Baltimore, MD, USA ISBN 978-1-939133-04-5 Open access to the Proceedings of the 27th USENIX Security Symposium is sponsored by USENIX. Efail: Breaking S/MIME and OpenPGP Email Encryption using Exfiltration Channels Damian Poddebniak1, Christian Dresen1, Jens Muller¨ 2, Fabian Ising1, Sebastian Schinzel1, Simon Friedberger3, Juraj Somorovsky2, and Jorg¨ Schwenk2 1Munster¨ University of Applied Sciences 2Ruhr University Bochum 3NXP Semiconductors, Belgium Abstract is designed to protect user data in such scenarios. With end-to-end encryption, the email infrastructure becomes OpenPGP and S/MIME are the two prime standards merely a transportation service for opaque email data and for providing end-to-end security for emails. We de- no compromise – aside from the endpoints of sender or scribe novel attacks built upon a technique we call mal- receiver – should affect the security of an end-to-end en- leability gadgets to reveal the plaintext of encrypted crypted email. emails. We use CBC/CFB gadgets to inject malicious plaintext snippets into encrypted emails. These snippets S/MIME and OpenPGP. The two most prominent stan- abuse existing and standard conforming backchannels to dards offering end-to-end encryption for email, S/MIME exfiltrate the full plaintext after decryption.
    [Show full text]
  • PHINMS Security White Paper Pdf Icon[230 KB, 8 Pages]
    On Securing the Public Health Information Network Messaging System Barry Rhodes Rajashekar Kailar Associate Director For Public Health System Development Chief Technology Officer Information Resources Management Office Business Networks International, Inc. Centers for Disease Control and Prevention www.bnetal.com www.cdc.gov Abstract The Public Health Information Network PHINMS is operating system neutral since it is Messaging System (henceforth, PHINMS) is the implemented using Java and J2EE standards. Centers for Disease Control and Prevention’s (CDC) implementation of the ebXML 2.0 Further, it provides language neutral, queue based messaging standards [EbXML]. This system was interfaces for sending and receiving messages. The developed for the purpose of secure and reliable preferred queue implementation is an messaging over the Internet. This software has ODBC/JDBC compliant database table, but been widely deployed by CDC and its public support for queues based on XML file descriptors health partners, including state and local health also exists. PHINMS supports peer-to-peer departments, and healthcare providers. PHINMS is messaging, as well as messaging via a third party designed to leverage X.509 digital certificates using a send and poll model. issued by public key infrastructures, but does not require a single, universal PKI. In this paper we Message data security is accomplished using a discuss some of the security aspects of PHINMS. combination of encryption, end-point authentication, and access control techniques. Introduction Transport reliability is accomplished using message integrity verification, transmission retries and duplicate detection on message receipt. The Public Health Information Network Messaging System (PHINMS) is a CDC Since PHINMS is used to transport sensitive data developed implementation of existing standards over public un-trusted networks (e.g., Internet), it for the secure and reliable transmittal of messages is important to make sure that end-points trust across the Internet.
    [Show full text]
  • Multi-Device Secure Instant Messaging
    SoK: Multi-Device Secure Instant Messaging Antonio Dimeo, Felix Gohla, Daniel Goßen, Niko Lockenvitz {antonio.dimeo, felix.gohla, daniel.gossen, niko.lockenvitz}@student.hpi.de Hasso Plattner Institute, University of Potsdam April 17, 2021 Abstract The secure multi-device instant messaging ecosystem is diverse, varied, and under- represented in academia. We create a systematization of knowledge which focuses on the challenges of multi-device messaging in a secure context and give an overview of the current situation in the multi-device setting. For that, we analyze messenger documentation, white papers, and research that deals with multi-device messaging. This includes a detailed description of different patterns for data transfer between devices as well as device management, i.e. how clients are cryptographically linked or unlinked to or from an account and how the initial setup can be implemented. We then evaluate different instant messengers with regard to relevant criteria, e.g. whether they achieve specific security, usability, and privacy goals. In the end, we outline interesting areas for future research. Contents 1 Introduction3 1.1 Group Messaging vs. Multi-Device Messaging............... 4 1.2 Methodology.................................. 4 2 Multi-Device Messaging7 2.1 Context...................................... 7 2.2 Transferring Data Between Different Devices of One User........ 7 2.2.1 Storing Data on a Server........................ 8 2.2.2 Using Messages to Exchange Data.................. 9 2.3 Transferring Data to a Different User..................... 11 2.3.1 Without End-to-end Encryption................... 11 2.3.2 End-to-end Encryption With Shared Group Key.......... 13 2.3.3 End-to-end Encryption Per Recipient...............
    [Show full text]
  • Google Message Encryption
    Google Message Encryption Automatic Encryption for Sensitive Email Communications ABOUT GOOGLE APPS Business requirements, industry regulations, and government mandates increasingly Google Apps is a suite of applications dictate that your organization must secure electronic communications. Whether it is that includes Gmail, Google Calendar financial data, medical records, or proprietary corporate information, you simply (shared calendaring), Google Talk must secure the delivery of sensitive content to its destination. Encrypting email (instant messaging and voice over IP), communications is a cost effective solution that helps your organization prevent Google Docs & Spreadsheets (online document hosting and collaboration), financial penalties and potential brand equity damage when sending unprotected Google Page Creator (web page proprietary or regulated data via email. creation and publishing), Start Page (a single, customizable access point for all applications) and Google Security & Compliance. Google Apps What Google Message Encryption Service Does offers editions tailored to specific customer needs, including the Google Message Encryption service, powered by Postini, provides on-demand Standard Edition (ideal for family message encryption for your organization to securely communicate with business domains), Education Edition (K-12 partners and customers according to security policy or on an “as needed” basis. schools, colleges and universities) and Premier Edition (businesses of Without the complexity and costs associated with legacy
    [Show full text]
  • Expert and Non-Expert Attitudes Towards (Secure) Instant Messaging
    Expert and Non-Expert Attitudes towards (Secure) Instant Messaging Alexander De Luca, Google; Sauvik Das, Carnegie Mellon University; Martin Ortlieb, Iulia Ion, and Ben Laurie, Google https://www.usenix.org/conference/soups2016/technical-sessions/presentation/deluca This paper is included in the Proceedings of the Twelfth Symposium on Usable Privacy and Security (SOUPS 2016). June 22–24, 2016 • Denver, CO, USA ISBN 978-1-931971-31-7 Open access to the Proceedings of the Twelfth Symposium on Usable Privacy and Security (SOUPS 2016) is sponsored by USENIX. Expert and Non-Expert Attitudes towards (Secure) Instant Messaging Alexander De Luca1, Sauvik Das2, Martin Ortlieb1, Iulia Ion1, Ben Laurie1 1Google; 2Carnegie Mellon University, Pittsburgh, United States {adeluca,mortlieb,iuliaion,benl}@google.com,[email protected] ABSTRACT curity/privacy over traditional mobile IMs have entered the In this paper, we present results from an online survey with app market. However, there are, as yet, few insights about 1,510 participants and an interview study with 31 partici- how and why users do or do not use these messengers. pants on (secure) mobile instant messaging. Our goal was To bridge this gap in the literature, we performed two stud- to uncover how much of a role security and privacy played ies – an online survey with 1,510 participants and a set of in- in people’s decisions to use a mobile instant messenger. In person interviews with 31 participants. For the interviews, the interview study, we recruited a balanced sample of IT- we recruited a balanced sample of people from the general security experts and non-experts, as well as an equal split public and IT security experts.
    [Show full text]
  • Fortimail Identity Based Encryption
    WHITE PAPER FortiMail Identity Based Encryption A Business and Compliance Enabler FORTINET – FortiMail Identity Based Encryption - A Business Enabler PAGE 2 Contents Business Need Secure Mail Delivery ............................................................................................................................. 3 Challenges with Available Technologies ........................................................................................................................ 3 Transport Layer Security (TLS/SSL) .......................................................................................................................... 3 S/MIME ....................................................................................................................................................................... 3 PGP ............................................................................................................................................................................ 3 FortiMail Solutions .......................................................................................................................................................... 4 FortiMail Overview ...................................................................................................................................................... 4 FortiMail Identity-Based Encryption ............................................................................................................................ 5 Identity-Based Encryption ..............................................................................................................................................
    [Show full text]
  • Secure Message Exchange on the Internet
    New York University Computer Science Department Courant Institute of Mathematical Sciences Secure Message Exchange on the Internet Course Title: Application Servers Course Number: g22.3033-003 Instructor: Jean-Claude Franchitti Session: 9 XML and Security Standards Various widely accepted security standards are available today to secure communication on the Internet. The most relevant standards, which include IPSec, Secure Socket Layer, S/MIME, and Pretty Good Privacy. IPS Security (IPSec) provides IP-level security and is widely used for Virtual Private Networks (VPNs). Secure Socket Layer (SSL) provides transport-level security and has become a de facto standard for secure HTTP connections. SSL uses X.509 certificates for authentication. SSL is a secure protocol in the session layer, and is being standardized by the IETF as the Transport Layer Security (TLS). Secure/Multipurpose Internet Mail Exchange (S/MIME) is the secure mail standard, and it also used X.509 certificates for authentication. Pretty Good Privacy (PGP) is the de facto standard for e-mail security. It can be used to send encrypted digital signatures and to encrypt stored files. SSL Secure Messaging Native SSL supports three of the four aspects of secure messaging including confidentiality, integrity, and authentication. SSL supports confidentiality via the use of a symmetric cryptosystem such as the Data Encryption Standard, and Ron’s Code (i.e., RC- 4). While DES uses a 56-bit key, RC-4 uses a 40-128 bits variable key length. SSL supports integrity via Message Authentication Code (MAC). MAC is based on a secure hash function such as Message Digest 5 (i.e., MD5) and Secure Hash Algorithm 1 (i.e., SHA 1).
    [Show full text]
  • Top 10 Questions to Ask Before Selecting a Secure Messaging Solution
    TOP 10 QUESTIONS TO ASK BEFORE SELECTING A SECURE MESSAGING SOLUTION SIMPLIFYING & SECURING ENTERPRISE MESSAGING Table of Contents Introduction . 3 Does the solution ensure HIPAA compliance? . 4 Does the solution integrate with existing applications? . 7 Is it an extensible secure texting platform? . 9 Is the secure texting application intuitive? . 11 Does the solution support admin control? . .14 Does the solution secure confidential information? . .16 Does the solution replace outdated or unreliable communication tools? . .19 Does the solution foster workflow collaboration or a collaborative environment? . .21 Does the vendor leave you in good hands? . 26 Does the solution have proven success? . 28 Conclusion . .31 Introduction Evaluating secure text messaging compiled the Top 10 Questions functional requirements, but solutions can be a time-consuming to Ask Before Selecting a Secure also fits their use case. Learn all and confusing process for health- Text Messaging Solution, allowing key aspects of a solution includ- care organizations, especially with you to simplify the selection ing technical requirements, key restrictive compliance regulations process and more easily identify functionality concerns, and how in place. Once you have realized what you need from your secure to determine a vendor’s proven the need for a secure texting texting vendor. success record with case studies solution, the research, evaluation and testimonials. and selection process could be Healthcare organizations can long and unorganized without the easily discover the top concerns necessary tools or understanding when evaluating secure texting of what your ideal solution would solutions and ensure the solution be. That is why TigerText has they select not only meets all 4.
    [Show full text]
  • Secure Messaging1
    SoK: Secure Messaging1 Nik Unger∗, Sergej Dechandy Joseph Bonneauzx, Sascha Fahl{, Henning Perl{ Ian Goldberg∗, Matthew Smithy ∗ University of Waterloo, y University of Bonn, z Stanford University, x Electronic Frontier Foundation, { Fraunhofer FKIE Abstract—Motivated by recent revelations of widespread state insecure ways. However, as will become clear over the course surveillance of personal communication, many solutions now of this paper, the academic research community is also failing claim to offer secure and private messaging. This includes both a to learn some lessons from tools in the wild. large number of new projects and many widely adopted tools that have added security features. The intense pressure in the past two Furthermore, there is a lack of coherent vision for the future years to deliver solutions quickly has resulted in varying threat of secure messaging. Most solutions focus on specific issues models, incomplete objectives, dubious security claims, and a lack and have different goals and threat models. This is com- of broad perspective on the existing cryptographic literature on pounded by differing security vocabularies and the absence of secure communication. a unified evaluation of prior work. Outside of academia, many In this paper, we evaluate and systematize current secure messaging solutions and propose an evaluation framework for products mislead users by advertising with grandiose claims their security, usability, and ease-of-adoption properties. We con- of “military grade encryption” or by promising impossible sider solutions from academia, but also identify innovative and features such as self-destructing messages [7]–[10]. The recent promising approaches used “in-the-wild” that are not considered EFF Secure Messaging Scorecard evaluated tools for basic by the academic literature.
    [Show full text]