diff options
Diffstat (limited to 'content/Getting_Started.tex')
| -rw-r--r-- | content/Getting_Started.tex | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/content/Getting_Started.tex b/content/Getting_Started.tex index bef3111..95cb69d 100644 --- a/content/Getting_Started.tex +++ b/content/Getting_Started.tex @@ -183,7 +183,7 @@ Use the following workflow set up a very basic Security policy. This gives you a Then you can select the tag you just created from the list. \item (\textcolor{gold}{Optional})Specify \textbf{Effective Devices} by choosing Device Tags or leave the value empty, which means the policy is effective on all devices by default. \item (\textcolor{gold}{Optional})Select a \textbf{Schedule} or leave the value set to always. - \item Verify that \textbf{Log Session} is enabled. Only traffic that matches the Security policy rule will be logged in Security Event Logs. + \item Verify that \textbf{Log Session} is enabled. Only traffic that matches the Security policy rule will be logged in Security Events. \item (\textcolor{gold}{Optional})Enter a \textbf{Description} for the rule. \item Verify that Enabled is enabled. \item Click \textbf{OK}. @@ -198,7 +198,7 @@ Use the following workflow set up a very basic Security policy. This gives you a \item Click \textbf{Verify} to execute the \textbf{Security policy match} test. \end{enumerate} \item[STEP 3.] After the policy has been hit, view Logs to monitor the policy rule status and determine the effectiveness of the policy rule. - Select \textbf{Logs} > \textbf{Security Event Logs} and view relative information about the policy. + Select \textbf{Logs} > \textbf{Security Events} and view relative information about the policy. \end{description} @@ -246,7 +246,7 @@ You can perform the following to set up a basic proxy policy. \\ \item Select the \textbf{Protocol} and \textbf{APP ID} from the drop-down. \item Click \textbf{Verify} to execute the Proxy Policy Match test. \end{enumerate} - \item[STEP 3.] Go to \textbf{Logs} > \textbf{Proxy Event Logs} and view \textbf{Logs} to monitor the policy rule status, verify if the proxy rule has been hit and determine the effectiveness of the policy rule. + \item[STEP 3.] Go to \textbf{Logs} > \textbf{Proxy Events} and view \textbf{Logs} to monitor the policy rule status, verify if the proxy rule has been hit and determine the effectiveness of the policy rule. \end{description} %\pdfbookmark[1]{Command Line Interface}{Command Line Interface} |
