DOCSLIB.ORG

Assessing the Security of Android Dating Apps Värdering Av

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Assessing the Security of Android Dating Apps Värdering Av DEGREE PROJECT IN COMPUTER ENGINEERING, FIRST CYCLE, 15 CREDITS STOCKHOLM, SWEDEN 2020 Assessing the Security of Android Dating Apps Värdering av säkerheten i dating- appar för Android HAMPUS HAUFFMAN ADAM MEYER KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ENGINEERING SCIENCES IN CHEMISTRY, BIOTECHNOLOGY AND HEALTH Assessing the Security of Android Dating Apps HAMPUS HAUFFMAN, ADAM MEYER Degree Programme in Computer Engineering Date: June 7, 2020 Supervisor: Shahid Raza Examiner: Ibrahim Orhan School of Engineering Sciences in Chemistry, Biotechnology and Health Swedish title: Värdering av säkerheten i dating-appar för Android iii Abstract Dating apps are continuously becoming a larger part of the social media mar- ket. Like any social media app, dating apps utilize a large amount of personal data. This thesis analyzes two dating apps and how they handle personal infor- mation from a security and privacy standpoint. This was done by conceptual- izing a threat model and then validating the threat through penetration testing on both of the apps in an attempt to find security vulnerabilities. This analysis proves that there is a substantial difference in whether or not app developers take security seriously or not. It was found that in one of the two apps analyzed, gaining access to personal data was particularly more trivial than expected, as TLS or other encryption were not implemented and server-side authorization was lacking in important app features like the one-to-one user chat. Keywords – Penetration testing, ethical hacking, dating apps, Android, reverse engineering, threat modeling, risk rating iv Sammanfattning Dating-appar blir kontinuerligt en större del av moderna sociala medier. Likt andra sociala medier utnyttjar dating-appar en stor mängd personlig informa- tion för att skapa relevanta matchningar med andra användare. Detta arbete analyserar två dating-appar och hur de hanterar känsliga personuppgifter med hänsyn till informationssäkerhet. Detta uppnåddes genom skapandet av en hot- modell (Threat Model) som senare validerades genom penetrationstestning av respektive app i ett försök att finna säkerhetssårbarheter. Sammanfattningsvis visar arbetet att det finns en tydlig skillnad mellan att utvecklare tar säker- het på allvar och att det underprioriteras. I en av de två apparna var tillgång till personliga data mycket enklare än vad som förväntades då appen saknade kryptering av trafik och var bristfällig i auktorisering av användare, speciellt i funktioner som en-till-en chatten. Contents 1 Introduction 1 1.1 Problem Definition . .2 1.2 Objective . .2 1.3 Limitations . .2 1.3.1 Attack Surfaces . .3 2 Background and Related Works 4 2.1 Security Threats and Risk . .4 2.2 Threat Modeling . .5 2.2.1 The STRIDE Method . .5 2.2.2 Risk Assessment . .6 2.3 The Android Platform . .7 2.3.1 Android Security Mechanisms . .7 2.3.2 The Google Play Store . .8 2.4 Online Dating Apps . .9 2.4.1 Dating App #1 . .9 2.4.2 Dating App #2 . .9 2.5 Publishing Security Concerns . .9 2.6 Related Works . 10 3 Method 13 3.1 Threat Model . 13 3.1.1 Identifying Assets . 14 3.1.2 Finding Threats . 15 3.1.3 Risk Rating . 18 4 Results 22 4.1 Reverse Engineering the Apps . 22 4.1.1 Reverse Engineering App #2 . 24 v vi CONTENTS 4.1.2 Reverse Engineering App #1 . 24 4.2 Tampering with API Requests . 25 4.2.1 Tampering with API Requests in App #2 . 25 4.2.2 Tampering with API Requests in App #1 . 26 4.3 Disclosure of Chat Messages . 27 4.3.1 Disclosure of Chat Messages in App #2 . 27 4.3.2 Disclosure of Chat Messages in App #1 . 28 4.4 Spoofing User Identity . 28 4.4.1 Spoofing User Identity in App #2 . 28 4.4.2 Spoofing User Identity in App #1 . 29 5 Discussion 30 5.1 Interpretations . 31 5.2 Implications . 31 5.3 Limitations . 31 5.4 Recommendations . 32 6 Conclusions 34 Bibliography 36 A HTTP Communication 38 A.1 HTTP Response When Fetching Chat Messages in App #2 . 38 A.2 Proof-of-Concept Script for Fetching Chat Messages in App #2 39 Chapter 1 Introduction As an increasing number of people are using online dating applications (apps), more and more personal data is being transmitted and stored by the companies developing the apps. To compete on a saturated market of these apps, devel- opers are focusing on extra functionality and ease of use such as user cloud storage or in-app messaging. This, however, raises the important question of how security and privacy are handled for user data. Apps in the dating app market are differentiated not only by their features but also by their number of downloads and active users. By examining two dating apps with different levels of popularity and production a light can be shed on how security and privacy is handled in Android dating apps regarding different scenarios and attack surfaces. The main objective of this report will be to assess the security of two Android dating apps by performing an initial threat modeling phase on each targeted app followed by penetration testing of the most crucial attack surfaces for the apps, respectively. By doing this on more than one dating app it will further highlight how security and privacy is handled in different scenarios, finan- cially and socially. The first app in question is one of a higher standard and downloaded by millions of users. The second app has a significantly smaller user base with a smaller budget, especially in regards to security. Both the apps are from the Google Play Store, written in either Java or Kotlin and are used on Android devices. 1 2 CHAPTER 1. INTRODUCTION 1.1 Problem Definition Mobile applications can be permitted to collect a large amount of personal in- formation such as physical location or other personal data that is required in dating apps, for example, users current location, sexual orientation and sexual preferences. One might therefore expect mobile apps to have more robust secu- rity measures than web-based implementations. However Qin, et al. [1] have shown in their work assessing the security of specifically online dating apps, that many popular dating apps have had the recurring vulnerability of fully disclosing victims’ location. This information could, in worst-case scenarios, easily be taken advantage of by cyber-stalkers but is already a major violation of user privacy. A paper by Patsakis, et al. [2], similar to the work by Qin, also shows recurring threats to private user data in dating apps. Patsakis’ work shows that many popular apps unintentionally disclose sensitive information such as sexual orientation, preferences, emails, the degree of interaction be- tween users and more. In accordance with the conclusions of Patsakis’ work, it is important to disclose security vulnerabilities to inform and engage the public in cyber security and privacy matters but also in order to question pro- gramming practices in place for dating apps. Is it possible to comprehensively assess the security of Android dating apps through penetration testing? 1.2 Objective The main objective of the project is to assess some general aspects of the secu- rity of Android dating apps and to convincingly demonstrate whether the sys- tem is secure or not through threat modeling, followed by a series of penetra- tion tests on chosen attack surfaces to validate the threat model. The category in question is online dating apps and the project will focus on the Android plat- form. Through threat modeling, a systematic process for identifying threats and potential attacks is set in place. A threat model identifies relevant attack surfaces to then be validated by attempting to find vulnerabilities through pen- etration testing. Not finding vulnerabilities after these steps can also attest to a sufficient implementation of security in the targeted system. 1.3 Limitations This project will only focus on the Android platform and the Google Play Store given that it is one of the largest mobile application markets and its largest CHAPTER 1. INTRODUCTION 3 competitor, Apple, has a more closed off platform and a more restricted mar- ketplace for app developers security-wise. Another delimiter for this project is the chosen scope in which to search for possible vulnerabilities as a fully qualified security audit would be too large of a project withing the given time frame. For identifying and validating threats on a more technical level, the project depends heavily on the decompiled source code for each of the dating apps. The source code can be statically analyzed in an attempt to find errors made by the developers. This also aims to show some contrast between a good and a bad app (security-wise) by showing their different implementations of core security principles. A completely comprehensive analysis of even one app would however be impossible for a team of two people within the timespan of a bachelor thesis. Time being a limiting factor, finding entry points and utilizing the threat model for efficient analysis is crucial. 1.3.1 Attack Surfaces The attack surfaces to be subjected to penetration testing will be chosen through threat modeling and risk rating. For a fair assessment of chosen dating apps, the threat modeling scope and methods must be comprehensive. Therefore, risk analysis for each threat will be used to also factor in likelihood and con- sequence. Only those threats that are most likely to occur and have the most critical consequences can then be chosen for validation through penetration testing, making for a more qualitative assessment. Denial of Service attacks will be viewed as out of scope for the penetration testing section of this project as there is usually no way to legally validate threats for this in a production environment not owned by the testers.
Load more

Recommended publications
  • Download Resume
    Oji Udezue http://www.linkedin.com/in/ojiudezue . +1 425-829-9520 SUMMARY: EXPERIENCED PRODUCT, DESIGN & TECHNOLOGY EXECUTIVE I’m a product-led growth expert. A multi-disciplinary tech exec with strong product, design and engineering leadership skills. I have had stints in marketing and sales which provide a well - rounded experience of key business functions. In addition, I have startup experience and a track record advising several great startups. I have a talent for new product strategy and the practical leadership to innovate and execute with conviction. I am passionate about early stage product development and entrepreneurship in organizations. My strongest skill sets are product vision, lean product management; strategy & planning, people management and talent development. Professional Experience CALENDLY VP of Product (2018 – Present) Lead Technology, Product, Design and Content Strategy • Under my tenure, Calendly is sustaining 100% year on year growth in ARR and MAU • Drive key engineering investments and a high-performance engineering culture • Set product vision, mission and goals for business • Drive ongoing, high velocity innovation • Manage overall user experience and delivery of value to customers • Manage team health, product craft excellence and talent acquisition • Drive clear and actionable business metrics and management of business to those metrics • Drive acquisition strategy; review and approve potential acquisition deals • Manage growth program and virality initiatives to increase audience share ATLASSIAN Head
    [Show full text]
  • Atlassian, a Devops Leader, Partners with Protiviti to Deliver Cutting-Edge IT Controls Across Its Environment
    CLIENT STORY Atlassian, a DevOps leader, partners with Protiviti to deliver cutting-edge IT controls across its environment Technology companies compete on their ability to quickly develop, deliver and update quality systems and software. This need for speed has led solution providers to abandon the traditional “waterfall” software development Keys to Success methodology in favor of Agile and DevOps, a faster and more collaborative approach that ultimately aims to enable faster time to market and a more reliable product. However, many organizations have struggled to apply Change requested traditional IT control frameworks within an Agile/DevOps environment, and the Embed control activities into Agile two are often misconceived as being incompatible. processes without compromising speed of delivery Atlassian, a global software development company responsible for creating Change envisioned team collaboration and productivity tools — including Jira, Confluence, Trello, Stride and BitBucket, among others — recognizes that trust is Combine Protiviti’s IT, risk and increasingly at the forefront of customer adoption considerations, and that compliance expertise with Atlassian’s key to demonstrating trustworthiness is being transparent with compliance. culture of innovation to design In addition, when it listed on the NASDAQ market in the United States in best-in-class controls in a DevOps December 2015, Atlassian needed to be in a position to demonstrate effective environment controls to its investors. Change achieved Embedded, automated controls
    [Show full text]
  • TEAM Q4-2019 Shareholder Letter
    Shareholder Letter Q4 FY19 and Fiscal 2019 | July 25, 2019 From the CEOs Fellow shareholders, Fiscal 2019 was another outstanding year for Atlassian. We surpassed 150,000 customers and vaulted past the $1 billion revenue mark for the first time in a fiscal year. This year also saw a number of important advances in our products aimed to better serve our customers: Trello Trello reinforced its status as a go-to collaboration tool in the workplace, serving more than 80% of the Fortune 500. In Okta's 2019 Businesses @ Work report, Trello was cited as the most widely adopted project management app at work. We introduced powerful organization-wide features for Trello Enterprise and made automation a more integral part of Trello with the addition of Butler for Trello. Jira family We improved the overall user experience of our Jira product family by simplifying the interface for new users and enhancing features for more advanced users. This combination of simplicity and power keeps Jira Software the industry standard for managing work in software teams. Cloud for We introduced an early access program for large enterprises, expanding enterprises support from 5,000 to 10,000 users. Cloud We introduced an early access program for Cloud Premium Editions of Jira Premium Software and Confluence targeting more sophisticated and larger customers. These new editions combine advanced end-user features with additional platform capabilities around uptime, service levels and data storage. Access We saw continued momentum from one of our newest products, Atlassian Access. Access provides company-wide security and policy administration across multiple Atlassian products, and already supports hundreds of thousands of users in its first year.
    [Show full text]
  • A Microsoft Office for Software Development with a Growing Moat, Large TAM and High-Quality Management
    Company: Atlassian (NasdaqGS: TEAM) Rainbow Chik Recommendation: Long [email protected] Price Target: $422 (79% upside/ 21% 3-yr IRR) A Microsoft Office for software development with a growing moat, large TAM and high-quality management KEY STATISTICS TRADING CHART EXECUTIVE SUMMARY Atlassian is a high-quality SaaS market leader that offers mission critical workplace collaboration and Application Development software. It is analogous to Microsoft Office for software development and is the oil that powers software development from planning, coding, deployment, support and collaboration. I believe TEAM is undervalued as the market (1) underappreciates TEAM’s moat expansion as a result of cloud migration, (2) underestimates TEAM’s strong network effect expanding in the large knowledge worker TAM, (3) overlooks management quality being long-term owner- operator and prudent capital allocator. The recently announced migration from perpetual licenses to cloud subscription presents a unique window to invest. Investors are concerned about the short-term revenue headwind and churn risk as a result of cloud migration, but my research suggests that it masked the better business potential given it leads to higher pricing power in a win-win situation and much stickier customers in the long-term. My base case valuation suggests a 79% upside from its current valuation at $236 ($423 target price). This is based upon sustained strong customer growth and subscription revenue per customer growth during and post-cloud-migration from my research. In addition, my bull/ bear case analysis suggests an attractive 3.5x upside/ downside ratio. COMPANY OVERVIEW Atlassian = Microsoft Office for software development Founded in 2002, Atlassian is an Australian SaaS market leader.
    [Show full text]
  • A Threat Modelling Approach to Analyze and Mitigate Botnet Attacks in Smart Home Use Case
    A Threat Modelling Approach to Analyze and Mitigate Botnet Attacks in Smart Home Use Case Syed Ghazanfar Abbas, Shahzaib Zahid Faisal Hussain Ghalib A. Shah, Muhammad Husnain Al-Khawarizmi Institute of Computer Al-Khawarizmi Institute of Computer Al-Khawarizmi Institute of Computer Science (KICS) Lahore, Pakistan Science (KICS) Lahore, Pakistan Science (KICS) Lahore, Pakistan [email protected] [email protected] [email protected] [email protected] [email protected] Abstract—Despite the surging development and utilization of hardcoded, or guessable passwords, lack of security updates, IoT devices, the security of IoT devices is still in infancy. The etc. [5]. The attackers first exploit these vulnerabilities, then security pitfalls of IoT devices have made it easy for hackers bypass the user’s privacy and information and finally use the to take over IoT devices and use them for malicious activities like botnet attacks. With the rampant emergence of IoT devices, victim IoT device to perform different malicious activities botnet attacks are surging. The botnet attacks are not only ranging from shutting down service to control over end devices catastrophic for IoT device users but also for the rest of the world. [6]. Therefore, there is a crucial need to identify and mitigate the The rampant emergence of IoT devices caused the ignorance possible threats in IoT devices during the design phase. Threat of security threats to large extent [6]. The security pitfalls modelling is a technique that is used to identify the threats in the earlier stages of the system design activity.
    [Show full text]
  • Moving Your Team from Hipchat to Slack: Part One
    Moving Your Team from HipChat to Slack: Part One In late July 2018, Atlassian announced it would be entering a “strategic partnership” with Slack. HipChat will shut down for good on February 15, 2019, which means that businesses using the service must be fully transitioned to Slack (or another collaboration platform) before that date. This news came as quite a shock to HipChat users, given Atlassian’s stated commitment to carving out its own corner of the busy real-time team communications market (the company released Stride, a new workplace communications product, just a few months ago). But Atlassian’s sudden and dramatic about-face was an inevitable reaction to the pressures of its chosen marketplace. Image: Slack’s Twitter announcement [email protected] 1 www.teampay.co Why Slack won Unlike Atlassian, Slack has been gaining market share at a remarkable rate: the company boasted in May that it had reached over eight million daily users and that 65% of the Fortune 100 companies were now paid Slack subscribers. Source: Slack Slack’s impressively broad integration options are a core component of its success; users of InVision, Trello, GitHub, Salesforce and many other popular SaaS platforms can install plug-and-play apps to link these platforms with Slack. That makes it a much “stickier” team collaboration option than, say, HipChat (which has a far smaller pool of available integrations) and greatly reduces customer churn. Whatever commercial software products and platforms you work with, there’s likely to be an app for that in Slack’s App Directory. Even direct competitors Google and Microsoft have worked with Slack to develop integration apps for their products.
    [Show full text]
  • TEAM Q2-2018 Shareholder Letter
    From the CEOs Fellow shareholders, We closed out calendar year 2017 with another strong quarter of fnancial, customer and product growth. Revenue for the quarter was $212.6 million, up 43% year-over-year, with free cash fow of $67.8 million. As of December 31, 2017 we counted 112,571 companies as customers, 4,825 of whom were added in the quarter. This is the most net new customers we've ever added in a single quarter and another milestone on our way to unleashing the potential of every team. We saw solid demand across all our deployment options—Cloud, Server, and Data Center. We continue to land and expand with customers of all sizes, and across numerous industries and geographies. Of course, results like these don't “just happen.” They're driven by product innovations that make our customers more productive, the incredible ecosystem of vendors that partner with us, and the vibrant community of users we connect with through events like the upcoming Team Tour—all of which you’ll hear more about below. We'll also touch on our expanding U.S. footprint and the newest member of our executive team. Jira Service Desk embedded portals: coming to a site near you No matter what business you're in, whether your customers are internal or external, they're demanding easier access to service. That's why Jira Service Desk users can now embed a mini help portal that lets their customers raise service requests from any web page on their website or intranet, without having to navigate to a separate page on a diferent part of the site.
    [Show full text]
  • Tenable Plugin for Atlassian Jira Manage Remediation Activities with Tenable and Jira (On-Prem)
    SOLUTION OVERVIEW TENABLE PLUGIN FOR ATLASSIAN JIRA MANAGE REMEDIATION ACTIVITIES WITH TENABLE AND JIRA (ON-PREM) BUSINESS CHALLENGE Security and IT teams utilize JIRA on-prem to plan, track and release fixes for their continuous security needs. Without the ability to integrate Tenable’s critical vulnerability intelligence with tracking and visualization capabilities of JIRA on-prem, this leaves them unable to prioritize and remediate based on their cyber risk. TECHNOLOGY SOLUTION COMPONENTS The Tenable integration for Atlassian JIRA on-prem combines the JIRA on-prem tracking • Tenable.io/Tenable.sc 5.13 or later platform with the vulnerability discovery capabilities of Tenable to deliver a comprehensive solution for teams to remediate their cyber risk. By ensuring that both platforms share • Atlassian JIRA 8 (On-Prem) information on vulnerabilities and their affected hosts, this integrated solution provides a cohesive platform for continuous visibility and critical context across the enterprise. KEY BENEFITS VALUE • Streamlines remediation The Tenable integration for JIRA on-prem provides: and tracking efforts • The ability to export Tenable vulnerabilities to visualize cyber exposure within JIRA • Reduces miscommunication on-prem between teams • To closely track your remediation efforts in JIRA on-prem with updated affected host information • Automatically create/close issues • A solution to close the knowledge gap between IT and Security teams which plague many modern enterprises; now, both teams can work from the same playbook of
    [Show full text]
  • A Smartphone-Based System for Clinical Gait Assessment Andres Alfredo Perez Leon University of South Florida, [email protected]
    University of South Florida Scholar Commons Graduate Theses and Dissertations Graduate School 6-30-2016 A Smartphone-based System for Clinical Gait Assessment Andres Alfredo Perez Leon University of South Florida, [email protected] Follow this and additional works at: http://scholarcommons.usf.edu/etd Part of the Computer Sciences Commons Scholar Commons Citation Perez Leon, Andres Alfredo, "A Smartphone-based System for Clinical Gait Assessment" (2016). Graduate Theses and Dissertations. http://scholarcommons.usf.edu/etd/6350 This Thesis is brought to you for free and open access by the Graduate School at Scholar Commons. It has been accepted for inclusion in Graduate Theses and Dissertations by an authorized administrator of Scholar Commons. For more information, please contact [email protected]. A Smartphone-based System for Clinical Gait Assessment by Andres´ A. Perez´ Leon´ A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Computer Science Department of Computer Science and Engineering College of Engineering University of South Florida Major Professor: Miguel A. Labrador, Ph.D. Sean J. Barbeau, Ph.D. Yu Sun, Ph.D. Date of Approval: April 6, 2016 Keywords: Physical Therapy, Gait Index, Android Copyright c 2016, Andres´ A. Perez´ Leon´ ⃝ DEDICATION To my parents for being the strongest pillars of my life, and to my girlfriend, for withstanding all this time far way from each other and constantly reminding me of keep pushing forward. None of this would be possible without all of you. Thank you. ACKNOWLEDGMENTS First and foremost, I wish to thank my major profressor Dr.
    [Show full text]
  • 8X8 Integrates with Atlassian to Modernize Communications, Collaboration, and Customer Engagement
    September 12, 2017 8x8 Integrates with Atlassian to Modernize Communications, Collaboration, and Customer Engagement SAN JOSE, Calif.--(BUSINESS WIRE)-- 8x8, Inc. (NASDAQ:EGHT), the world's first Communications Cloud provider, today announced it is teaming up with Atlassian Corporation Plc (NASDAQ:TEAM), a leading provider of team collaboration and productivity software, to develop and go to market with integrated unified communications, contact center, collaboration, and team messaging solutions. This will speed up adoption of 8x8 and Atlassian solutions, enabling mid-market and enterprise companies to modernize business communications, collaboration, and customer engagement for increased productivity, enhanced customer experience, and accelerated time to revenue. "Customer engagement is everyone's business and this is driving convergence in the fast-growing collaboration and cloud communications markets, enabling midmarket and enterprise companies to deliver an enhanced customer experience. Atlassian is well-recognized as a leader in the team collaboration space, especially in the world of DevOps (development operations)," said Bryan Martin, Chairman and CTO of 8x8. "As a Gartner Magic Quadrant for Unified Communications as a Service, Worldwide leader for six years running, 8x8 is ready to become the de facto voice for DevOps by teaming with Atlassian." As mid-market and enterprise companies continue to unify their communications and team collaboration systems to enhance business productivity, accelerate time to revenue, and increase profitability, 8x8 will integrate 8x8 Virtual Office® Unified Communications as a Service (UCaaS) with Atlassian HipChat team collaboration. This will offer customers seamless access to telephony, video, meetings and messaging — all from within HipChat rooms with all notes synced with Confluence content collaboration software.
    [Show full text]
  • Ongoing Program Results
    Atlassian Collaboration tools for teams of all sizes Atlassian Bugcrowd Ongoing program results Report created on July 31, 2018 Report date range: July 01, 2017 - July 31, 2017 Prepared by Ryan Black, Senior Director of Security Operations [email protected] , [email protected] Table of contents 1 Executive summary 3 2 Reporting and methodology 4 3 Targets and scope 5 4 Findings summary 7 5 Appendix 9 6 Closing statement 11 Bugcrowd Ongoing Program Results | Atlassian 2 of 12 Executive summary Atlassian engaged Bugcrowd, Inc. to perform an Ongoing Bounty This report is just a summary of the Program, commonly known as a crowd-sourced penetration test. information available. All details of the program's findings — An Ongoing Bounty Program is a cutting-edge approach to an comments, code, and any researcher application assessment or penetration test. Traditional penetration provided remediation information — tests use only one or two personnel to test an entire scope of work, can be found in the Bugcrowd while an Ongoing Bounty leverages a crowd of security researchers. Crowdcontrol platform. This increases the probability of discovering esoteric issues that automated testing cannot find and that traditional vulnerability assessments may miss in the same testing period. The purpose of this engagement was to identify security vulnerabilities in the targets listed in the targets and scope section. Once identified, each vulnerability was rated for technical impact defined in the findings summary section of the report. This report shows testing for Atlassian's targets during the period of: 07/01/2017 – 07/31/2017. For this Ongoing Program, submissions were received from 85 unique researchers.
    [Show full text]
  • Cycle Atlanta SWIFT Development (Project Number 2016-007)
    2017 Final Report Cycle Atlanta SWIFT Development (Project number 2016-007) Author: Dr. Kari Watkins, Ph.D., Georgia Institute of Technology April 2017 Cycle Atlanta SWIFT Development – 2016-007 DISCLAIMER AND ACKNOWLEDGMENT OF SPONSORSHIP “The contents of this report reflect the views of the authors, who are responsible for the facts and the accuracy of the information presented herein. This document is disseminated under the sponsorship of the U.S. Department of Transportation’s University Transportation Centers Program, in the interest of information exchange. The U.S. Government assumes no liability for the contents or use thereof.” i Cycle Atlanta SWIFT Development – 2016-007 TABLE OF CONTENTS Abstract ........................................................................................................................................... 1 Background ..................................................................................................................................... 2 Research Approach and Applications ............................................................................................. 5 Migrating to Swift .............................................................................................................5 Updating the Event Model ................................................................................................5 Process for Updating .........................................................................................................5 Conclusions, Recommendations, and Suggested
    [Show full text]