tags
We’re still buzzing from the incredible conversations at FieldHub Build25 in Baltimore. While we spent most of the conference diving deep into platform updates and industry trends, we wanted to do something a little different this year – and it turned out to be one of the most valuable sessions we’ve ever hosted.
We brought together an absolutely stacked panel of cybersecurity experts (their words, but we completely agree): Michael Sussman, who chairs Fenwick’s privacy and cybersecurity practice and was one of the earliest leaders in the field; Laura Galante, former director of the Cyber Threat Integration Center; and Jon Lenzner, former chief of staff to the FBI director. Alexis Serfaty, Director of Geo-Technology at Eurasia Group, moderated what became one of the most engaging and practical security discussions many attendees had ever experienced.
After almost two-decades in the field service industry, first running Urban Alarm and now leading FieldHub, I’ve encountered many of the same frustrations that security and fire alarm installers and integrators face when it comes to the software tools they rely on. The lack of ownership, combined with outdated, piecemeal software solutions, has been a persistent issue. This challenge isn’t just about inefficiency and weak support; it’s about the very foundation on which businesses are built—technology.
Choosing the right merchant service provider for credit card and ACH processing can impact your customer experience and your bottom line. In this post, we walk through some factors to consider when selecting your merchant service provider.
PCI is the Payment Card Industry Data Security Standard for information security. Due to the time-consuming nature of seeking PCI compliance, you should avoid systems and workflow where you need to bear responsibility for PCI compliance on your office workstations and internal processes. Specifically, you should partner with vendors that handle PCI compliance within their own framework.
With today’s global reality, we wanted to take the opportunity to share some of our favorite resources to help security installers acclimate to a remote working model.
From the very beginning, we built FieldHub around distributed teams. We have key team members in the US, Canada, and Europe. Even before launching FieldHub, I ran my security integration business, Urban Alarm, with distributed teams. From accounting and HR to provisioning video servers and IP cameras, our team members were dispersed across the globe. We shared one of our configurations for remotely provisioning IP gear in a previous post here.
The conditions of Spring 2020 have more of us working from home than the office. As we all face these new challenges, I wanted to share guidance to ease one part of that transition: best practices in the area of remote IP device configuration.
Urban Alarm - the security integrator business I started in 2008 and sold in 2017 - was built from the ground up, using distributed teams. In addition to accounting and HR functions being performed largely remotely, most of our system configuration was done overnight, using remote teams.
