Skip to main content

Instructor, no.

Incydr Professional, Enterprise, Gov F2, and Horizon, no.

Incydr Basic, Advanced, and Gov F1, no.

CrashPlan Cloud, no.

Retired product plans, no.

CrashPlan for Small Business, no.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Introduction to Incydr

...

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/p[2]/span[1], line 1, column 10
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/p[2]/span[2], line 1, column 10
brings together three dimensions to quickly and accurately detect and help you respond to insider risks and potential threats:

...

...

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/h3/ins/span, line 1, column 10
Alerts

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/p[1]/span, line 1, column 10
 lets you know when important data may be leaving your company through the use of
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/p[1]/a/ins/span, line 1, column 10
Alerts

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/ins[1]/span, line 1, column 10
Alerts automatically notify you about file activity occurring along a number of exposure vectors. You can create multiple alert rules to alert you for different exposure types, severities, and users causing the file activity. 

...

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/p[3]/span, line 1, column 10
can also recover files, including deleted files and previous file versions. During an investigation you can restore a single file, multiple files, or even an entire device, allowing you to inspect the contents of the files involved.

...

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/p[5]/span, line 1, column 10
monitors file activity via a light-weight agent on endpoints and integrations with corporate cloud and email services

, mitigating file exposure and exfiltration risks without disrupting legitimate collaboration. 
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[1]/ins[2]/span, line 1, column 10
 is smart enough to know there's a difference between everyday collaboration and the events that represent real risk. It filters out the noise of harmless activity, like sharing files between trusted domains, to reveal only the risks that could harm your business.
.

...

No blocking

Traditional data-loss prevention (DLP) attempts to obstruct data movement in real time, but the system is only as good as your rules. Make rules too sensitive and you block legitimate work. Make rules too specific and high-value data slips past your defenses. DLP can only see what it's looking for and that can leave blind spots in your security stack.

We believe that the new path to data loss prevention and security compliance starts with one core principle: monitor everything, regardless of its sensitivity or perceived value.

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ins[3]/span[1], line 1, column 10
leverages broad and deep visibility into ALL data activity and user behavior to better understand true risk. 
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ins[3]/span[2], line 1, column 10
does not rely on classification of data to identify exfiltration events, but instead correlates data, vector, and user information to improve signal.

For the times you feel compelled to block, we recommend you take action on the user, not the data. For example, you can use identity and access management to put users in groups to restrict access based on the alerts and information
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ins[4]/span, line 1, column 10
provides.
 

For more information about why we don't block, download our guide.

...

  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/li[1]/span, line 1, column 10
    
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/li[2]/span, line 1, column 10
    
     
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/li[3]/span, line 1, column 10
    
     
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/li[4]/span, line 1, column 10
    
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/li[5]/span, line 1, column 10
    
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/li[6]/span, line 1, column 10
    
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Introduction_to_Incydr), /content/body/div[2]/ul/ins/span, line 1, column 10
    
    joint solution brief:
     Code42 Incydr + Okta Identity Cloud

Other changes:

  1. /body/ul[3]/li/a[2]/@data-mce-href:
  2. "mailto:csmsupport@code42.com" ⇒ nothing
  3. /body/ul[3]/li/a[2]/@href:
  4. "mailto:csmsupport@code42.com""/Terms_and_conditions/Code42_customer_support_resources/Get_support_for_CrashPlan_for_Small_Business_or_Code42_CrashPlan"
  5. /body/ul[3]/li/a[2]/@rel:
  6. "external nofollow" ⇒ nothing
  7. /body/ul[3]/li/a[2]/@target:
  8. "_blank" ⇒ nothing
  9. /body/ul[3]/li/a[2]/@title: nothing ⇒
  10. "/Terms_and_conditions/Code42_customer_support_resources/Get_support_for_CrashPlan_for_Small_Business_or_Code42_CrashPlan"
  • Was this article helpful?