Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.
Explanation: As I said in my discussion entry, these "Regeln" are called "directives" in most cases, and often the config file of server programs allows for directives to be processed/evaluated/interpreted/considered/read according to a priority order which may in turn be configurable; if there are no matches, some default directive applies.
This is especially true for IP addresses, e.g. a server may be configured not to listen to a certain group of hosts (not to allow requests from an IP address range or network segment) but with an exception for one or two hosts from that group (which is why the config. is as flexible/complex as described). Or for instance, a network print server may deny certain users (i.e., hosts) access to certain printers in the printer pool, and normally it identifies those hosts via their IP addresses. Many other server or program functions may be configurable according to that scheme, which is used in many applications. S the same logic may apply to programs which are not servers, in which case "rule" might be a more suitable term for "Regel".
"Parsed", as suggested by me earlier, is also possible. You may also say "evaluate", etc, depending on the rest of your translated phrase. Not sure about "traversed".
This seems to be a very typical server directive dealing with access rules based on IP addresses/address ranges/network mask, where you always have to define which rule has the higher/lower priority.
Regelablauf und Priorität
Die Priorität der Regeln wird nach den folgenden Kriterien definiert.
In Abhängigkeit von der in einem ’Adress-Template’ vorhandenen Menge an IP-Adressen, ergibt sich die folgende Priorität:
• einzelne IP-Adresse
• Adressbereiche
In Abhängigkeit zur Regelnummer, ergibt sich die folgende Priorität:
• Die Regeln werden der Priorität nach von Regel 1 (oben) nach Regel 4 (unten) durchlaufen.
• Trifft eine Regel zu, wird die dazu definierte Aktion ausgeführt. Alle darunter liegenden Regeln werden dann vernachlässigt.
• Trifft keine Regel zu, wird die Default-Regel angewandt.
a) What is the source document talking about ?
b) In what kind of a situation does the term appear?
c) Any thoughts on the translations you are considering or have ruled out ?
Automatic update in 00:
Answers
3 hrs confidence: peer agreement (net): +1
processed / evaluated
Explanation: As I said in my discussion entry, these "Regeln" are called "directives" in most cases, and often the config file of server programs allows for directives to be processed/evaluated/interpreted/considered/read according to a priority order which may in turn be configurable; if there are no matches, some default directive applies.
This is especially true for IP addresses, e.g. a server may be configured not to listen to a certain group of hosts (not to allow requests from an IP address range or network segment) but with an exception for one or two hosts from that group (which is why the config. is as flexible/complex as described). Or for instance, a network print server may deny certain users (i.e., hosts) access to certain printers in the printer pool, and normally it identifies those hosts via their IP addresses. Many other server or program functions may be configurable according to that scheme, which is used in many applications. S the same logic may apply to programs which are not servers, in which case "rule" might be a more suitable term for "Regel".
The translation workplace 
peer agreement (net): +1
