Watch a one minute video
THREE STEPS TO FILE SECURITY
EXTENSIVE VALIDATION CRITERIA OPTIONS
Process or child thread from which access is being requested.
Module from which access is being requested
Number of instances of a protected element are already running.
Other process in (or not in) the host device’s memory.
GPS location testing (supporting inclusive or exclusive polygons).
BIOS setting in (or not in) the host device.
Installed hardware on (or not on) the host device.
Internet address(es) assigned (or not assigned) to the host device.
Local file system contents present (or not present).
Custom (user-written) criteria.
MAC address(es) assigned (or not assigned) to hardware on the host device.
Windows registry contents for devices hosting a Windows OS.
Remote controls base on contents of specific files and/or results of program execution.
Images of the user and environment (for camera-equipped devices)
Recordings of auditory environment (for audio-equipped devices).
Time (includes date) controlled invocation within ranges, length, patterns, etc…
Known Virtual Machines being run in an environment.
Logged-on user or user group membership information.
User keyboard and mouse activity (or lack thereof).
Proactive criteria (see Code Cocoon™ documentation)
Use Case Examples
In this situation, all criteria about the device itself (BIOS tag, IP address, etc…) would all be common across users. Each individual has their own account information in order to log onto the machine. The logged-on username (along with group memberships) is one of the many criteria an AMULET ™ can use to define access to an individual file.
AMULETs ™ have a number of criteria which can be defined to prevent robotic use of a digital asset when a user is not present. AMULET ™ criteria can be defined to require that a user be logged on, even a specific user, and further that there be mouse, keyboard, or touchscreen activity within a certain timeframe of any AMULET ™ lease request or lease request validation. AMULETs ™ can have time criteria defined to block any use of a digital asset during certain time periods the user is known to be unavailable.
No matter what the reason or need, AMULETs ™ can be restricted to devices based on what specific file(s) are (or are not) installed on the device, what processes are (or are not) active on the device, or from which modules in a process an access request is coming from. For example, the author could identify a file uniquely associated with the conflicting application, and could then create AMULET ™ file criteria that would deny access to the author’s application if the offending file was present on the host device.
GLOBAL CHALLENGE. WORLD CLASS RESPONSE.
Covers all platforms. The only solution capable of working without regard to the device platform.
Operating system agnostic. The only solution capable of working without regard to the operating system.
Fail-safe design. Default is to protect the digital asset.
Resolves today’s (and tomorrow’s) cybersecurity industry issues.
QUESTIONS YOU MUST ASK YOUR SECURITY PROVIDER
Traditional data security protects containers, not the contents within them. This is known as Container-Related Asset Protection, also referred to as Endpoint security.
Containers are things like third-party browsers, operating systems, file systems, server farms, or cloud infrastructure. Once a container is breached, any assets within the container are defenseless.
Historically, and even today, so-called “new security techniques” are simply derivatives of the same Container-Related Asset Protection, as providers simply provide additional layers.
Certitude Digital has been featured in Forbes magazine… “Security Overhauls Are More Essential Than Ever For Financial Companies”
“Why do companies continue to follow the same archaic security
strategies while data breaches are at an all-time high?”
Losses Due to Cybersecurity Breaches
As Projected by Industry Leaders**
** Cybersecurity Market Report – Cybersecurity Ventures | Industry and Security News – Lavasoft | Computer Business Review | Juniper Research