FortiGate policies
Define authorised application traffic and document the purpose, owner and review conditions of firewall rules.
Fortinet
Fortinet FortiGate for SMEs in French-speaking Switzerland: firewall rules, segmentation, site connectivity and documented administration with Sunitech.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

A firewall sits between the applications, users and networks that need to communicate. A Fortinet FortiGate project starts by identifying those exchanges and the people who approve them. Sunitech helps SMEs in French-speaking Switzerland document their internet access, sites, remote users and internal services. The selected architecture should explain which flows are authorised, where they pass and how changes are reviewed.
Define authorised application traffic and document the purpose, owner and review conditions of firewall rules.
Separate user groups, servers, guest devices and technical equipment according to the exchanges they need.
Prepare addressing, routing and supported secure tunnels between business locations with representative connectivity tests.
Assess remote access and authentication options against the installed FortiOS version and your working practices.
Select inspection functions with their performance impact, licensing and subscriptions checked against the intended use.
Organise useful event records, administrative access and recoverable configuration copies for maintenance and incident review.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Identify sites, equipment, traffic and dependencies before defining priorities.
Prepare changes, test configurations and organise commissioning.
Assess usage, coverage areas and mobility needs. The required measurements are agreed during scoping.
Separate uses, restrict traffic and define access rules with the people responsible.
Agree monitoring checks, updates and incident-handling arrangements.
Document the network and plan its next developments with your teams.
We start with your teams’ needs, business applications and organisational constraints.

Share client files between colleagues, with appropriate access and documents that are easy to find.

Keep tills and connections working, including across multiple shops.

Protect patient records and maintain the tools needed for consultations.

Connect the office and the workshop, secure equipment and prepare for recovery after an incident.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Defined areas and needs, with coverage to be checked on site.
Traffic rules and separate access according to usage.
Inventoried equipment and checks suited to the required service.
Updates and changes prepared with the people involved.
Useful documentation for planning replacements and new requirements.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Sizing considers the traffic to inspect, the number of connections and the functions that will be enabled. Interface capacity alone does not establish performance under every inspection profile. We check the current model documentation, licensing and subscription requirements against your workload. An IT audit can bring together the existing topology, service dependencies and constraints before a firewall is replaced.
Network segments and firewall policies should reflect your business responsibilities. We identify users, servers, guests and technical equipment, then document the exchanges each group needs. Rules have an owner, a reason and a review process. A pilot checks important applications before a wider change. Cybersecurity support also considers administrative access, privileged accounts and the evidence needed to understand an incident.
Connecting sites or enabling remote work requires more than creating a tunnel. We review addressing, routing, identity checks and the applications that must remain available. The supported VPN methods and authentication options depend on the FortiOS version and deployment. Before switching over, we agree test cases, a maintenance window and conditions for returning to the previous configuration if a critical service does not work.
Logs need a purpose and someone responsible for reviewing them. We agree useful events, retention requirements and escalation contacts. Configuration copies should be available to authorised people alongside a record of versions and changes. Updates are planned with prerequisites and their possible effect on connectivity. IT support can provide an agreed contact point for incidents and controlled changes throughout the equipment lifecycle.
Does every FortiGate offer the same functions? No. Hardware, software version, licensing and subscribed services must be checked for the intended design.
Can a firewall replace all other security controls? No. Endpoint protection, identity management, backups and the people responsible for alerts remain part of the wider protection arrangements.
Use the official FortiGate documentation portal and the FortiOS administration guide to check policies, network design and prerequisites. Apply the guidance for the software version installed in your environment.
Review of your needs, comparison of options and clearly explained priorities.
Preparation, configuration, testing and coordination with the relevant providers.
Agreed support scope, documentation, licences and next steps.
A project? A question?
An initial conversation to understand your situation and decide on the next steps together.
Contact us