ACTIMIZE
Strength
 Effective real-time and non real-time
risk scoring engine prevents online
and real-time payment fraud
 Effective at preventing real-time
and non-real-time cross-channel
fraud (Web, call center and
interactive voice response [IVR]
across the enterprise, where
criminals use multiple channels to
perpetrate their crimes
 Web offering is part of an enterprise
fraud management platform, so if
integrated, modules can benefit
from common user profiles, shared
models, rules, policy, and alert and
case management systems and
processes
 It forms strong partnerships with its
strategic large customers
 Flexible API’s that enable customers
to provide and manage the data that
they need in their application
 Case management system
integrates alerts from non Actimize
external systems
 It makes easy for business users to
write their own rules and scenarios
 It can work with and ingest multiple
types of authentication and device
identification data and protocols
 Its implementations are relatively
straightforward if users integrate
legacy applications through Actimize
APIs as opposed to having to build a
data warehouse to support the
application
 The Actimize Policy Manager
enables users to manage and deploy
rules for non-Actimize systems that
may play a large role in online
banking an online payments
Caution
 Expert professional post-
implementation services are scarce
 Implementation is difficult and take
much longer
 Difficult to get assistance from
qualified staff when special tuning or
customization work needs to be
done
 Implementation require on-site
assistance for several months to
properly fine tune the models and
ENTRUST
 Can listen to and block transaction in
real-time, and helps prevent account
takeovers and man-in-the-browser
attacks
 Good, flexible rule based system
computes scored based on the
weighting assign to the rules
 Has real-time alerting – and user
applications can integrate with an
API to IdentityGuard for real-time
transaction blocking.
 Listener can listen to all relevant
traffic (e.g. user logins, application
navigation and transactions)
 Listener software is easy to maintain
and operate
 Data mart stores all the web
application data
 Has good prioritization of alerts
(low, medium, high), also a clear
visible association between the alert
and the rule that kick it off.
 Easy for business users and fraud
analysts to add their own rules, for
example when there is a new type of
attack
 Creates profiles of users stored in
user database tables that keep track
of variables associated with user
activity
 Reporting system is supposed to
have greatly improved with the
latest software version, based on
open-source Jasper
 Alert management is now tightly
integrated with reporting
 Has been proven in mobile banking
fraud detection, and it is developing
and implementing other cross-
channel capabilities
 Storage requirements are very large
 Uses a rule-based system, so there
are lots of rules to establish and
learn
 Difficult to configure complex rules
 Because it’s so flexible and under
user control, you must think hard
about new rules that are added so
that you don’t create overwhelming
amounts of alerts and/or stored
RSA
 Provides hosted services and on-
premises software to help prevent
account takeover
 Supports WFD in a variety of use
cases
 Risk scoring uses the Bayesian
predictive model plus a rule engine,
and it offers real-time and offline
risk-scoring models
 Has a good case management tool,
overall alerting is also very good –
users get back information as to
what caused and constituted the
alert
 Basic link analysis is provided
 Supports “back-coloring” process
that take new fraud findings and
applies them to historical records
where fraud may have been missed
 Has satisfactory basic reports – daily
and real time
 Easy for users to add their own
rules and set thresholds
 Provides some, and integrates with
many, authentication factors
 WFD is integrated with RSA’s anti
phishing and anti-malware
cyberintelligence service
 Can monitor any event type, even
customized ones, as long as the user
enterprise feeds RSA the data for
fraud scoring
 It has early integrations with mobile
banking and with call center
services. It compares activity across
the call center and the web channel
in batch mode
 Easy to implement/install a basic
version of the version
 Uses Web services
 Some users have complained about
model performance degradation
during the past year or more
 Model performance can deteriorate
if a fraudster passes the
authentication challenge and the
model does not flag the transaction
as suspect; however, enterprises do
not have to integrate authentication
with risk scoring
 Users cannot build their own
 scoring engine, and to customize
system interface
 Complex system, difficult to
understand and manage
 Poor reporting functionality
 Project delays result from rigid data
extraction, transformation and
loading processes if the system
requires a data warehouse for
operation
 Less experience with the specific
needs of other country beside U.K
and U.S
data
 Reporting system in older versions
was based on Business objects and
was severely limited; user must
upgrade to the software version
released in 3Q09 for improvement
 Decrypting encrypted data to parse
it results in system slowdown, albeit
acceptable; this is true for any
application monitoring encrypted
data
complex rules
 Users can sometimes get the wrong
information from U.S technical staff
that messes up implementations
 Users need to pay extra for a
primary account manager and go to
person
 Users can’t combine and nest
rules(but can prioritize them)
 Its front-end GUI does not enable
users to correlate all the data they
are interested in analyzing