Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Panamajack
New Contributor

Fortigate 81E Semi Admin User block edit of specific Policy Rule or Interface possible ?

Hi all,

 

I have several Fortigate 81E on different Branch Offices in use. SuperUser is always me & my team. But on some Branch Offices we have a Techi. For these Techi i already made some Read-Only User just to have a look at Policy and Logs if something gets blocked e.g. . As these branch offices are kinda independent they sometimes install severs that need to communicate with the outside world. This can happen if nobody of my team is at work. That's why im Wondering if its possible to give the Tech people at these branch offices write permission for the Firewall Policy, but deny them the use of some interfaces (this owuld be the interfaces to our internal network as their networks are DMZ and we only want several ports open to our network) or if its possible to mark several Firewall Policies as not editable for them ?

 

I'm pretty sure this won't work with the WebUI but maybe it's possible through cli ? 

 

Thanks in advance!

 

Alex

3 REPLIES 3
ede_pfau
SuperUser
SuperUser

Nope, not that I know of. GUI and CLI are equivalent in this point.

Either customer techie has to wait and cannot set up servers at any arbitrary time during the day/week.

Or, you secure your network from your side of the policy. Which will not keep him from creating traffic to other ports.

In the end, it's a question of who is responsible if a config change created a security risk. The one willing to take the blame will get the authorization. This should be the one with the most experience and knowledge.

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Panamajack

Thanks Ede!

 

Well than i guess me and my team will be the only one that can create policy rules. 

ede_pfau

[thumbs up!]

If I find someone has changed the config on a FGT that I manage I decline responsibility right away. No intention to play hide and seek.

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors