IoT, cloud and network security engineering

Security that holds when one layer fails.

LayereDefense protects building automation, metering and sensor systems, builds the cloud and network environments behind them for federal agencies, and prepares defense contractors for Cybersecurity Maturity Model Certification (CMMC) Level 2. Every engagement is led and delivered by senior engineers.

  1. Governance and policy
  2. Identity and access
  3. Network and segmentation
  4. Cloud, servers and endpoints
  5. Logging and response

Each layer is built on the assumption that the one above it has already failed.

  • Since 2016Ten years of security engineering
  • Service-disabled veteran-ownedSmall business
  • Zero Trust by designEvery device, user and connection is verified
  • Doctoral leadershipLed by a Doctor of Science in Cybersecurity

Services

Services drawn from work already delivered.

Everything below comes from engagements completed for federal agencies and for the companies that support them.

Core practice

IoT and building automation security

Building automation controllers, utility meters and environmental sensors were never designed to defend themselves. LayereDefense designs, builds and operates the network, server, cloud and monitoring layers that protect these Internet of Things (IoT) and operational technology (OT) systems, and has done so since 2017 at more than 150 locations around the world.

  • Segmented networks for controllers, meters and sensors
  • One tested build for every site: firewall, routers and switches
  • Windows and Linux servers hardened for the building software
  • Certificates, hardened device images and multi-factor sign-in
  • Central logging, monitoring and threat hunting
How the systems are protected

Focus

CMMC Level 2 readiness and hardening

Defense contractors that handle Controlled Unclassified Information (CUI) must meet the 110 security requirements of National Institute of Standards and Technology (NIST) Special Publication 800-171 to reach CMMC Level 2. LayereDefense builds and hardens the environment that the assessment examines, and keeps it compliant through the year.

  • Gap assessment against the 110 requirements
  • Enclaves in Microsoft 365 GCC High and Azure Government
  • Identity, device and endpoint hardening
  • System security plan, evidence and tabletop exercises
  • Year-round upkeep, ready for the annual affirmation
How the CMMC work is done
  • System hardening

    Windows and Linux servers, workstations and the systems that run artificial intelligence (AI) models, configured to a published security baseline, patched and logged. The work is done on the systems an organization already runs, and every setting is documented.

    • Windows servers, workstations and virtual desktops
    • Linux servers and device images
    • AI systems kept inside the boundary, with controlled access and logging
    • Published baselines, including Security Technical Implementation Guides (STIGs)
  • Cloud architecture, government and commercial

    Landing zones, hybrid connectivity and delivery pipelines in Microsoft Azure and Amazon Web Services (AWS), in the commercial regions and in the government ones, written as code so that the environment can be reviewed, rebuilt and audited.

    • Azure and AWS landing zones, commercial and government
    • Terraform, pipelines and container platforms
    • Account and cost governance
  • Network engineering

    Firewalls, routers, switches and site-to-site connections that are designed, configured and tested before they ship, for networks that span many sites and have to keep running when a link fails.

    • Firewall, router and switch builds
    • Type 2 encryptors
    • Site-to-site and cloud connectivity
    • Upgrades, migrations and troubleshooting
  • IT leadership for defense contractors

    Fractional IT director services and day-to-day operations for small defense technology companies that must meet government security requirements without a full IT department of their own.

    • Microsoft 365 GCC High administration
    • Device management through Intune
    • On-site and remote operations support
  • Security assessments

    Independent reviews that measure an environment against the framework that applies to it and end with a ranked list of fixes that the organization can act on.

    • Federal control frameworks (NIST SP 800-53, RMF)
    • Health care and payment card standards (HIPAA, PCI DSS)
    • Microsoft 365, IoT and OT audits
    • Incident investigation and tabletop exercises
  • Automation and private AI

    Logging pipelines, infrastructure automation and AI assistants that run on hardware the client controls, so that operational data stays inside the organization.

    • Splunk and syslog pipelines
    • Operations automation
    • Self-hosted language models
  • Training and exercises

    Hands-on training built around realistic scenarios, from capture-the-flag (CTF) ranges to workshops for administrators and end users.

    • Instructor-led cybersecurity courses
    • CTF ranges
    • Conference talks and workshops

Selected work

Delivered, not proposed.

  1. Federal · IoT and OT

    Building and sensor networks at more than 150 locations

    Designed, and continues to operate, the network security architecture behind building automation, utility metering and environmental sensors at more than 150 government facilities around the world, from the firewall, router, switch and server builds at each site to the cloud services and central logging behind them. The system was carried through federal security authorization and is built as a Zero Trust architecture, in which every device, user and connection has to prove itself.

  2. Federal · Building automation

    Building systems, mapped and measured

    Audited the IoT and OT networks behind a federal agency's building systems against published standards, beginning with a map of what was really connected. On another system, hardened the building automation supervisors with multi-factor sign-in and a move to a current operating system.

  3. Federal · Cloud

    From no cloud to an approved environment

    Took a federal bureau from no cloud presence to an approved Microsoft Azure Government environment, with hybrid links to its existing networks, delivery pipelines and container platforms, and provided its cloud architect and technical lead.

  4. Defense industry · CMMC

    CMMC Level 2 environments for defense contractors

    Prepared several defense technology companies for CMMC and provided their IT director function. The work has included gap assessments, enclaves built in Microsoft 365 GCC High, device management through Intune, virtual desktops hardened to Security Technical Implementation Guide (STIG) baselines and the daily administration that keeps those environments in order.

  5. Assessments

    Measured against the standard that applies

    Assessed small businesses against the Health Insurance Portability and Accountability Act (HIPAA) and the Payment Card Industry Data Security Standard (PCI DSS). Other assessments have covered a Microsoft 365 environment, the security and IT operations of a private company, a public health benefit exchange and IoT and OT networks measured against published standards. The work has also included the investigation of a security incident, reconstructed from audit logs.

  6. Training

    Teaching by doing

    Taught cybersecurity courses as instructors, built capture-the-flag ranges for hands-on training and presented at the BSides Rochester and BSides Charleston security conferences.

Approach

The name is the method.

No single control is trusted to hold. Each layer of an environment is designed on the assumption that the one before it has already failed, and each engagement follows the same four steps.

  1. Measure

    The work starts with what exists: the network as it is cabled, the cloud as it is configured and the policy as it is actually followed.

  2. Design

    The architecture is written down and, wherever the platform allows, written as code that can be reviewed before anything is built.

  3. Build

    The engineers who designed the environment build it. The work is not handed down to a junior team.

  4. Operate and hand over

    Monitoring, runbooks and documentation are part of the delivery, so that the client can run the environment without outside help.

  • Senior hands onlyClients work directly with the engineers who do the work, from the first call to the final handover.
  • Everything as codeInfrastructure, policy and configuration live in version control, where changes can be reviewed and reversed.
  • Evidence over opinionFindings are measured and documented, and recommendations are ranked by the risk they remove.

About

A small firm on purpose.

LayereDefense LLC is a service-disabled veteran-owned small business, founded in 2016, based in Tampa, Florida, and led by a Doctor of Science in Cybersecurity.

The firm's experience runs from network engineering for large federal systems integrators to cloud architecture for federal agencies. That background shapes the work: environments are built to pass an audit and to keep working after the audit is over.

LayereDefense stays small so that the people a client speaks with are the people who do the work. When an engagement needs more hands, the firm adds senior specialists and works alongside the client's own staff and its prime contractors.

Company data

Legal name
LayereDefense LLC
Founded
2016
Headquarters
Tampa, Florida
Business type
Service-disabled veteran-owned small business
Leadership
Doctor of Science (D.Sc.) in Cybersecurity
Staff certifications
CISSP, CISM
Platforms
Azure Government, AWS, Microsoft 365 GCC High, Terraform, Splunk, Cisco

Contact

Tell us what you need to secure.

Email is the fastest way to reach the firm. A short description of the environment and the timeline is enough to start a conversation.

info@layeredefense.com
Office LayereDefense LLC
501 E Kennedy Blvd, Suite 1400
Tampa, FL 33602