now go set fire flow complements
existing change management systems with
intelligent automation that enables IT
to process firewall changes more quickly
and with less risk in this demo we'll
examine how fire flow seamlessly
integrates with BMC remedy to eliminate
the need for opening and tracking change
requests in multiple systems there are
two options for integrating fire flow
with remedy you can use fire flow as the
system to create the initial change
request and have it sync with remedy or
you can create the ticket and remedy and
have a subsequent request generated in
fire flow let's examine in the first
option where tickets are initially
created in fire flow in our example
Rachel needs tell that access to server
1 so she logs in to fire flow and
creates a new change request where she
enters the pertinent information into
fire flow such as source destination and
service and also adds a note to the
network administrator who will be
reviewing the ticket after submitting
the request Rachel sees a confirmation
page that shows the change request
process has started in fire flow with a
ticket number 48 assigned additionally
there's a link to that ticket that has
been subsequently created in remedy
clicking on this link takes us to the
remedy system where we can see that the
information Rachel entered into fire
flow is also populated in this master
system in the notes section all the
information from fire flow is populated
here in XML format take note of the risk
level it currently defaults to a blank
as the risk hasn't been determined yet
now let's jump back into fire flow as an
administrator to begin to change
workflow I found the ticket created by
Rachel notice the link to remedy is
there as well now I can start the
initial plan which checks to see if
traffic is blocked and requires action
by analyzing and simulating the routing
tables and firewall rule sets alko SEC
fire flow can identify unneeded changes
and automatically close a request in
this case we see that the traffic is
indeed blocked and that it is a valid
change request we also see that the
device impacted is a checkpoint firewall
if we click next we see the link to the
subsequent ticket in remedy which has
all this information
another intelligent step of algo set
fire flow is risk check by clicking risk
check fire flow automatically simulates
the impact of the proposed change based
on the network topology and routing and
analyzes this against algis X knowledge
base of best practices regulatory
requirements as well as the
organization's custom security policy
and compliance requirements in this
situation no risks were found now let's
switch back over to remedy to see how
the ticket has progressed in that system
since the risk check and fire flow found
no issues we can see that the risk level
has changed from the default of blank to
level 5 which is the company's lowest
defined risk level now that the risk
check is complete let's approve the
ticket in remedy now we're ready to plan
and schedule the change but first let's
switch back to fire flow to see how the
ticket has progressed in that system
back in fire flow we can see that the
ticket has been approved and we can now
create the work order notice in the
rural comment that the remedy ID is
included with all the other information
from the planning part of the workflow
we can now continue to implement the
change as with all fire flow tickets the
change request will be resolved
validated and fully audited and all the
information will be synchronized with
the remedy system this was a short
demonstration of how alga set fire flow
seamlessly integrates with remedy you
can request a free evaluation at algo
set calm / eval
