{"id":45854,"date":"2020-04-20T12:15:43","date_gmt":"2020-04-20T18:15:43","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=resource&p=45854"},"modified":"2021-02-12T18:24:37","modified_gmt":"2021-02-12T23:24:37","slug":"case-study-paywith-compliance-remote-work","status":"publish","type":"resource","link":"https:\/\/jumpcloud.com\/resources\/case-study-paywith-compliance-remote-work","title":{"rendered":"PayWith Case Study: Compliance, Remote Work, & System Insights"},"content":{"rendered":"\n
PayWith<\/a> develops mobile-centric payment and rewards solutions for businesses, which they can use to improve customers\u2019 commerce experiences.<\/p>\n\n\n\n Todd Wade, head of information security and compliance, helped PayWith search for and introduce its first directory three years ago, as well as transition to remote work when the COVID-19 pandemic forced businesses worldwide to reassess their operations.<\/p>\n\n\n\n Three years ago, PayWith operated without a directory \u2014 the company\u2019s developers took a \u201cgo-your-own-way\u201d approach. The need for centralized IT management became clearer as the company grew, and the team wanted to achieve SOC 2 compliance, which also required formalized access control.<\/p>\n\n\n\n <\/p>\n\n\n\n Todd previously spent more than a decade running IT operations for a credit union, which had a much more traditional and entrenched on-premises system. At PayWith, he knew he needed to find a directory solution that better suited its cloud-forward approach.<\/p>\n\n\n\n \u201cI figured it would be too long of a conversation to try to introduce a traditional setup like Active Directory\u00ae<\/sup>,\u201d he said. \u201cThat\u2019s when I started looking around to try to find something that would fit in with how they want to do things.\u201d<\/p>\n\n\n\n Todd began searching for a cloud directory service that he could use to introduce centralized IAM. PayWith works heavily in AWS\u00ae<\/sup> and GCP\u00ae<\/sup>, and it has since its founding. He wanted the directory he selected to reflect that.<\/p>\n\n\n\n \u201cIn the beginning, using cloud service providers was a cost-saving measure because there wasn\u2019t a huge outlay of cost to get a platform up and running,\u201d Todd said. \u201cOnce that happened, then it became a question of: Why have anything on-site?\u201d<\/p>\n\n\n\n He also wanted to implement security controls to lock down the company\u2019s systems \u2014 macOS\u00ae<\/sup>, Windows\u00ae<\/sup>, and Linux\u00ae<\/sup> machines \u2014 but in a way that was lightweight enough to satisfy the developers.<\/p>\n\n\n\n \u201cThe main thing I wanted to accomplish was to check all the boxes that SOC 2 required,\u201d he said. \u201cThe other thing was \u2014 coming from an IT management perspective \u2014 I wanted to slip in a bunch of controls that I needed to be able to manage the system.\u201d<\/p>\n\n\n\n Todd ultimately selected 探花大神\u00ae<\/sup> because its Directory-as-a-Service\u00ae<\/sup> satisfied all his requirements and allowed him to execute IT management from a single platform, rather than cobbling together and managing separate vendors for each individual need.<\/p>\n\n\n\n \u201cKnowing that I needed access management, knowing that I needed to support Windows, Mac, and Linux, and knowing that it was only me doing IT management, I wasn\u2019t looking seriously at solutions that couldn\u2019t support everything,\u201d he said.<\/p>\n\n\n\n PayWith achieved SOC 2 compliance with 探花大神, and the team is now preparing for a PCI audit as well. When he rolled out 探花大神, Todd also took the opportunity to roll out other security policies to PayWith\u2019s users. He implemented password controls and security configurations, such as a policy to lock screens<\/a> after a certain period of inactivity and policies to enforce full disk encryption<\/a>.<\/p>\n\n\n\n \u201c探花大神 was easy to put in place and get done what I needed to get done without anybody complaining about it,\u201d he said.<\/p>\n\n\n\n Todd recently rolled out 探花大神\u2019s premium System InsightsTM<\/sup><\/a>, which returns key telemetry about machine fleets. He\u2019s already used the feature to get the serial numbers on machines, which he wasn\u2019t always able to access previously. He\u2019s also used it to monitor network information and see where individual machines are located. He plans to incorporate other data points to monitor patch status, Chrome extensions and Firefox add-ons, and user SSH keys.<\/p>\n\n\n\n \u201cRolling out System Insights was as easy as it possibly could be. All of a sudden, I had a whole bunch of extra information coming into the system. It was great.\u201d<\/p><\/blockquote>\n\n\n\n Three years in, Todd continues to find and implement new features. They\u2019re easy to use and have enabled his use of 探花大神 to grow with PayWith.<\/p>\n\n\n\n \u201cThrough regular conversations with our 探花大神 account rep, I\u2019ll find out there are all these new services that are really easy to roll out, and it\u2019s just a matter of clicking them,\u201d he said.<\/p>\n\n\n\n In March 2020, Todd needed to transition the company to a work-from-home model, and the process was seamless. He went remote several days before the rest of the company, and he spent about half an hour getting everybody settled in the day the office officially went remote. He didn\u2019t have to do much other than help people get familiarized with new conditions.<\/p>\n\n\n\n \u201cI wish there was something more to talk about in terms of how easy it was for everyone to go remote,\u201d he said. \u201cI didn\u2019t have to worry about how they were going to connect to the directory server or how the firewalls needed to be set up so people were able to access everything. It was really just a matter of, \u2018OK, well, just pick up your laptop and go home.\u2019\u201d<\/p>\n\n\n\n 探花大神 has helped PayWith maintain a lean but secure IT operation, and it\u2019s been able to run in the background so Todd has more time for other tasks. With a directory that he\u2019s able to \u201cset and forget,\u201d he can now focus on essential tasks like working with AWS and GCP.<\/p>\n\n\n\n \u201cIT is all going to the cloud, at least for a lot of businesses,\u201d he said. \u201cIt doesn\u2019t make sense to spend 90% of your time in those areas but then have to come back and deal with on-prem systems. It wouldn\u2019t fit with how we run things.\u201d<\/p>\n\n\n\n Learn more about how PayWith helps organizations develop<\/a> innovative payment and rewards programs.<\/p>\n\n\n\n Whether you\u2019re looking for an IAM tool to help you achieve regulatory compliance or transition to remote work, 探花大神 is here to help. Click here to learn more about securely connecting user identities<\/a> to systems, apps, files, and networks from the cloud.<\/p>\n","protected":false},"excerpt":{"rendered":" PayWith needed a central cloud directory service to centralize identity and access management and achieve SOC 2 compliance.<\/p>\n","protected":false},"author":89,"featured_media":45857,"template":"","categories":[23],"collection":[],"wheel_hubs":[],"platform":[],"resource_type":[2313],"funnel_stage":[],"coauthors":[],"acf":[],"yoast_head":"\n<\/figure><\/div>\n\n\n\n
Background: Access Control & Compliance Goals<\/h2>\n\n\n\n
Head of Information Security & Compliance, PayWith <\/em><\/figcaption><\/figure><\/div>\n\n\n\nChallenges: Introduce a Directory without Adding Hardware<\/h2>\n\n\n\n
The Solution: 探花大神<\/h2>\n\n\n\n
Transition to Remote Work <\/h2>\n\n\n\n
The Result: \u2018Going to the Cloud\u2019<\/h2>\n\n\n\n
Learn More<\/h2>\n\n\n\n