# Cybersecurity Services in Alaska > Firewalls, segmentation, identity and multi-factor, endpoint, logging and secure remote access for Alaska organizations, from Trybus Solutions. *Source: https://trybussolutions.com/alaska/cybersecurity/ · Trybus Solutions · Chattanooga, TN · 423-633-1817 · info@trybussolutions.com* ## What We Do 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](https://trybussolutions.com/cybersecurity/) is set out on its own page. ## Why Alaska Organizations Bring Us In - **We are not tied to one manufacturer.** We carry a range of technology partners, so what we recommend is not decided by what we happen to sell. Sometimes the answer is to consolidate and sometimes it is to leave a control alone. - **Our engineers have done the rollouts.** Our security staff hold credentials including CISSP and CISM, with delivery history behind them. Knowing which questions to ask before a policy goes into enforcement keeps a change window from becoming an outage. - **We design for sites with nobody on site.** A firewall at a remote site has to be managed, updated and recovered from somewhere else. We plan remote administration and out-of-band access from the start, because a bad change at a site reached by air cannot be fixed by walking to the closet. - **We start from what is running now.** Rule bases that grew over a decade, accounts nobody owns, and vendor connections opened for a project that finished years ago. That inventory is unglamorous, and it is where the risk sits. - **One team sees the network and the security on it.** Segmentation, remote access and identity all depend on how the network is actually built. One team across both closes the gap that opens between separate vendors. - **We will tell you what does not need buying.** Some findings are worth fixing this quarter, some are worth scheduling, and some are worth writing down and accepting. We say which is which, even when it costs us a line on the quote. [Start a conversation](https://trybussolutions.com/contact-us/?service_solution=cybersecurity) ## What You Get 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. - **Assessment of the current environment:** Rule bases, identity sources, agent coverage and remote access paths, read from the live systems rather than the documentation. - **Findings, priorities and recommendation:** What we found, ordered by exposure and by the effort to fix it, and what the environment has to satisfy for regulators, contracts and insurers. - **Design documentation:** Segmentation, policy structure and naming, at the level of detail the build needs. - **Access and identity model:** Who gets access to what, how it is granted and removed as people join and leave, and how privileged and service accounts are handled. - **Remote and vendor access design:** Who connects from outside, to what, and how that access is granted, logged and taken away again. - **Bill of materials:** Hardware, licensing and services itemized, so procurement works from real numbers and renewals are visible early. - **Cutover plan and acceptance criteria:** Stages, change windows, the way back out of each stage, and what has to work before each one is signed off. - **As-built documentation and runbooks:** What was built, how it is configured, and the routine tasks your team will run afterwards. ## The Security Areas We Work In Six areas, and most projects touch more than one. ### Perimeter and Segmentation 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. ### Identity and Multi-Factor Authentication 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. ### Endpoint 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. ### Logging, Detection and Response 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. ### Remote and Third-Party Access 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. ### Devices That Will Not Take an Agent 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. ## How a Project Runs in Alaska 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. - **Scoping and kickoff:** Agree what is in scope, the deliverables, who is involved and how decisions get made, including who signs off on a change that could lock people out. - **Discovery:** Sessions with the people who run the environment now, plus configuration pulled from the live systems. When discovery changes the scope, we price it and you decide before we carry on. - **Design and review:** Design documented, then walked through with your team and whoever owns the applications it touches. - **Procurement and staging:** Hardware and licensing ordered, configured and staged, and shipped to remote sites ready to install. - **Pilot:** On larger projects a site or a group of users goes first, with a way back. On smaller ones this stage often is not worth the time, and we will say so. - **Rollout:** Site by site, or group by group. A policy being enforced for the first time stays in monitor mode long enough for the exceptions to surface. - **Handover:** Closer support while the snags come out, then documentation, training and a decision about the equipment being replaced. ## What Is Quoted Separately 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. - [Frameworks, control mapping and audit evidence. Choosing a framework, mapping controls to it, writing policy and assembling what an assessor asks for is its own engagement, run by our governance and compliance team.](https://trybussolutions.com/governance-risk-compliance/) - [Ongoing monitoring and operation. Running the environment after handover and watching the alert queue is a separate agreement with its own service levels. Plenty of clients keep that in house.](https://trybussolutions.com/alaska/managed-it-services/) - [Network design and physical infrastructure. Segmentation often exposes a network design question underneath it. Design is ours; cable is installed by the cabling partners we bring in. Each piece is priced on its own.](https://trybussolutions.com/alaska/network-wifi-sd-wan/) - [Device fleet and workplace rollout. Getting an agent onto every machine and running the fleet afterwards is a workplace project, usually owned by a different part of IT.](https://trybussolutions.com/digital-workplace/) - **Formal certification and attestation.** A certificate comes from an independent assessor, and it has to, because the document means something only if the person signing it did not build the environment. ## Who We Work With in Alaska The controls do not change much between sectors. What they protect, and who is asking about them, does. ### [Tribal Health and Tribal Government →](https://trybussolutions.com/tribal-organization/) Sovereignty over data, systems shared between government, health and enterprise, and security work paid for in funding cycles. ### [Hospitals and Clinics →](https://trybussolutions.com/healthcare/) Patient data, medical devices that cannot be patched, and clinics with no security staff on site. ### [Boroughs, Cities and State Agencies →](https://trybussolutions.com/public-sector/) Public records, procurement rules, and services that cannot go offline while an incident is investigated. ### [Alaska Native Corporations →](https://trybussolutions.com/enterprise/) Subsidiaries with their own networks, their own insurer questionnaires and, for some, federal contract requirements. ## Technology We Work With 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. [See all technology partners →](https://trybussolutions.com/partners/) ## Talk to Us About Security in Alaska 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. [Start a conversation](https://trybussolutions.com/contact-us/?service_solution=cybersecurity) [Insights and guides](https://trybussolutions.com/resources/) ## Related guides - [Network segmentation without stopping the business](https://trybussolutions.com/network-segmentation-without-stopping-the-business/) - [What a network refresh actually involves](https://trybussolutions.com/what-a-network-refresh-involves/)