Partner Perspectives  Connecting marketers to our tech communities.
09:00 AM
Raymond Pompon
Raymond Pompon
Partner Perspectives
Connect Directly

The Startup Challenge: Safe in the Cloud from Day One

How a Seattle travel company built a rock-solid mobile app without sacrificing performance or security.

Some startups see security as a nice-to-have that can be added months or years after launch. The smart ones realize that dependable security from the beginning means solid performance, satisfied customers, and no precious startup dollars wasted on fraud or incidents. F5 Labs decided to peek under the hood of one of these smart startups: Wanderlust Society. This Seattle-based company was created by a team of Amazon veterans looking to reduce the hassle while increasing the enjoyment of travel planning. Wanderlust Society created a Web application that wrangles the long tail of personalized recommendations and the online community for travelers looking to take and share highly curated trips.

Before you begin building your architecture, it’s a good idea to have a well-defined idea of what you want. Wanderlust Society thought this through and set the following as the primary goals for their Web application:

  • Mobile optimized
  • Secure
  • Fast
  • Highly available
  • Easily scalable

Understand Security Risks
To build a security risk model, you use these goals to anticipate potential threats. It's not enough to just say things like, "we want our site to be secure." Security can mean different things to different organizations, so risks needs to be detailed. The risk model will be used by developers and architects to make tradeoffs.  Wanderlust Society did an excellent job of defining these:

Unauthenticated users should only be able to read or write data and APIs that are explicitly marked publicly available.

  • Authenticated users should only be able to see and change their own data.
  • Authenticated users should see shared data from other users.
  • Authenticated users should not be able to read or write system data.
  • Attackers should not be able to access the system by stealing an authenticated user’s credentials.
  • Attackers should not be able to steal/scrape Wanderlust Society data.
  • Attackers should not be able to intentionally crash, degrade, or modify site functionality.

This list is by no means carved in stone. It can and should be reviewed periodically and updated as conditions changed.

Architect to Meet Goals and Address Risks
Once Wanderlust Society figured out goals and risks, they worked out architecture and security controls, including the following:

Mobile Optimized
For a powerful mobile experience, the site needed to be super-fast to load (ties to Fast goal), so the core JavaScript is only 90 KB (compressed). This means that the site works great even on a slow 3G mobile connection.

Wanderlust Society built their application in the cloud and they also correctly realized that application security in the cloud is their responsibility. That means they had to build and configure the proper tools to lock things down to their specific risks.

First, the application was designed to respond only to HTTPS requests, so all communication is encrypted. Second, the application was partitioned with firewalls and rules locking down traffic in both directions (to reduce attack surface and exfiltration). Databases are in a restricted, non-public subnet and firewalled to a single port. This reduces the risk of attackers stealing data from users.

Passwords are a common way to authenticate, but they are also fragile and a burden to manage properly. Wanderlust Society chose an alternate method and went with Federated Identity. This means their Web application pulls from another trusted authentication repository such as a third-party website where a user is already registered. Wanderlust Society chose to federate from Facebook because most people already have a Facebook account. Also, Facebook's infrastructure and platform are used by billions daily, so they’ve been proven reliable and secure.

To securely track users, Wanderlust Society used a request/access token system for all service calls. When a user authenticates, he or she is granted a token tied to the originating client device. Because you never want to trust user input, the token is constantly verified at the server side.

Since Wanderlust Society recognized that user input can never be trusted, they also built in server-side data validation checks and parameterized SQL statements to prevent injection attacks.

As described in the mobile optimized goal, the Wanderlust Society application was designed to be fast. In addition to the app design, they also leveraged cached content delivery networks at the edge for all site images as well as frequently used data.

Highly Available
Being Amazon veterans, the app developers are experts at leveraging Amazon Web Services (AWS). The server instances run in Elastic Compute Cloud (EC2) behind load balancers while CloudWatch is used for monitoring and alarming. Multi-availability zones are also deployed.

Easily Scalable
Wanderlust Society application services are based on the microservices architecture model where applications are small and generally focused around a small set of closely related tasks. This allows services to be independently deployable and expanded. Code is hosted in Docker containers within the EC2 instances, which is scalable to meet Wanderlust Society requirements.

There are always tradeoffs. One big one was using Facebook to federate identity. A minority of people don't trust Facebook and refuse to use their service, and some people are just not interested in signing up with Facebook. Those potential customers will probably not choose to join for now. Supporting federated identities allowed Wanderlust Society to push the development work of building their own secure account creation and login functionality to a future time when they have more resources. A worthwhile tradeoff, since building an authentication system from scratch requires expertise and thorough testing.

The second tradeoff was using the cloud versus an on-premises solution. Here, Wanderlust Society went back to its core mission: building software that helps people travel, not IT operations. So off to the cloud.

Wanderlust Society is off to a strong start with shrewd practices, including articulating their goals, doing a risk analysis against those goals, and choosing appropriate responses to counter those risks while weighing the tradeoffs.

Get the latest application threat intelligence from F5 Labs.


Raymond Pompon is a Principal Threat Researcher Evangelist with F5 labs. With over 20 years of experience in Internet security, he has worked closely with Federal law enforcement in cyber-crime investigations. He has recently written IT Security Risk Control Management: An ... View Full Bio
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: On the SS7 network, nobody knows you're a dog.
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-01-16
"deny-answer-aliases" is a little-used feature intended to help recursive server operators protect end users against DNS rebinding attacks, a potential method of circumventing the security model used by client browsers. However, a defect in this feature makes it easy, when the feature is i...
PUBLISHED: 2019-01-16
To provide fine-grained controls over the ability to use Dynamic DNS (DDNS) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit the types of updates that can be performed by a client, depending on the key used when sending the update ...
PUBLISHED: 2019-01-16
An error in handling certain queries can cause an assertion failure when a server is using the nxdomain-redirect feature to cover a zone for which it is also providing authoritative service. A vulnerable server could be intentionally stopped by an attacker if it was using a configuration that met th...
PUBLISHED: 2019-01-16
Under some conditions when using both DNS64 and RPZ to rewrite query responses, query processing can resume in an inconsistent state leading to either an INSIST assertion failure or an attempt to read through a NULL pointer. Affects BIND 9.8.8, 9.9.3-S1 -> 9.9.9-S7, 9.9.3 -> 9.9.9-P5, 9.9.10b1...
PUBLISHED: 2019-01-16
A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS64 feature and other preconditions were me...