We assess, design and build firewalls, segmentation, identity, endpoint protection and secure remote access for organizations in Alaska, including sites with no IT staff in the building.
Trybus Solutions assesses, designs and builds the security controls around an organization's network, users and devices: firewalls and segmentation, identity and multi-factor authentication, endpoint protection, logging and detection, and secure access for staff and vendors who connect from outside.
Most of this work starts for one of a few reasons. An insurer or a customer has sent a questionnaire the environment cannot answer honestly. A firewall estate is coming up on end of support. An audit has produced findings with dates attached. Or an acquisition has joined networks that were never designed to meet.
Alaska adds its own considerations. An organization can have sites hundreds of miles apart with no IT staff on site, equipment vendors who support their systems remotely, and staff who sign in from wherever they are working. Alaska's Personal Information Protection Act also sets breach notification duties for organizations that own or license personal information on Alaska residents, including written notice to the Attorney General before deciding that residents do not need to be told. Your counsel decides how that applies to you.
Our clients usually have their own IT team, and often somebody who owns security as part of a wider job. We are there for the parts that need people who have built this before. The wider scope of our cybersecurity, identity and secure access work is set out on its own page.
Scope varies. A firewall refresh at two sites does not need the documentation an identity rollout across an organization does. Below is what we produce on a typical mid-size project, and we agree which of it you need at scoping.
Everything we produce is yours. If you take the design elsewhere to be built, it will be complete enough for somebody else to build it.
Six areas, and most projects touch more than one.
Firewalls at the main office and every remote site, and the boundaries between clinical, government, guest and building systems. We inventory the rule base, agree the policy, then enforce it in stages so nothing stops without warning.
Single sign-on, multi-factor authentication, privileged accounts and the joiner and leaver process. Enrollment has to work for staff who travel, and for people signing in over a slow link at a remote site.
Protection software, hardening, disk encryption and patching for laptops and servers spread across the state. What matters is the share of machines that report in healthy, and on day one that is rarely the number the console shows.
What to collect, how long to keep it, and detections that mean something in your environment. Shipping logs from remote sites uses bandwidth those sites may not have, so collection is designed around the links.
Access that gives staff and vendors the applications they need rather than a route into the whole network. Equipment vendors who support their systems remotely often hold the oldest and least controlled access on the network.
Building systems, cameras, medical devices and industrial controls. Protection software cannot be installed on most of them and an aggressive scan can knock one over, so discovery is passive and segmentation carries the load.
Broadly the same shape whether it is a firewall pair at one site or an identity rollout across the organization. Timescales depend on the size of the estate, the state of the documentation and how much of your team is available.
Most of what is below is work we do. It is not part of a security project by default, because each piece carries its own scope, its own schedule and its own cost. If you want any of it included, say so at scoping and we will quote it in. The last one is different: it is work we do not do at all.
The controls do not change much between sectors. What they protect, and who is asking about them, does.
Sovereignty over data, systems shared between government, health and enterprise, and security work paid for in funding cycles.
Patient data, medical devices that cannot be patched, and clinics with no security staff on site.
Public records, procurement rules, and services that cannot go offline while an incident is investigated.
Subsidiaries with their own networks, their own insurer questionnaires and, for some, federal contract requirements.
We hold partner relationships across the security industry, and our engineers also work in platforms we do not sell. A project starts on whatever is protecting the environment now, whoever supplied it.
We do not publish comparisons between manufacturers. Which platform suits an organization is something an assessment works out, not something a website should decide.
Tell us what prompted the question, whether that is an insurer, an audit or an incident, and how many sites are involved. We will tell you what we think needs doing and what does not, and put a scope and a number against it.
We measure how this site is used, and we share visit data with Apollo, a third party who identifies the company behind a visit so we can follow up on genuine interest. This runs unless you decline. No advertising profiles are built. How this works
