ShareFile eFileCabinet Integration

You can enable the integration from the upper right after you have signed into your e File Cabinet Online account. Enable the integration from the menu shown below. After clicking ShareFile, you may enter the login information associated with your account.

User-added image

Once enabled and successfully linked, you can manage files without compromising security, as well as share files using the ShareFile Email System from the Share drop-down menu.

User-added image

For more information on how to use e FileCabinet Online and the ShareFile integration, please refer to eFileCabinet documentation.

Related:

  • No Related Posts

“The IP Address 185.153.222.46 was found to have a negative reputation.”

I need a solution

We have been receiving “The IP Address 185.153.222.46 was found to have a negative reputation.” error for months and our mails cannot be delivered. We are a legit company and we are sure that we are not sending and spam or soliciting emails. When we request our ip to be cleared, it is cleared for a while but then, gets to the “bad reputation” list again in a short time. I searched the forum but could not find a solution to this matter. Could you please help us to resolve the issue and clear our ip permanently?

Thanks in advance!

0

Related:

  • No Related Posts

How can I disallow TLS 1.1 for the session between the user’s device and the Proxy SG?

I need a solution

Hi;

My understandins is that the TLS version setting under Configuraiton> SSL> SSL client are for the ssl session between the Proxy SG and the Server, so you can disallow TLS 1.1 between the Proxy SG and the OCS “Server”.

My question is:

How can I disallow TLS 1.1 for the session between the user’s device and the Proxy SG?

Kindly

Wasfi

0

Related:

  • No Related Posts

Why denied category “denied” is not marking in the access log

I need a solution

Hi Team,

I have blocked categories “File Storage/Sharing” and “Email”. When proxy is hitting “Email” category it is showing “DENIED” message in logs. But when Proxy hitting “File Storage/Sharing” category. It is denirying the access but not shwoing DENIED message in logs.

Why it is like that?  It has show in Access logs the same status?

Thanks,

Mayur

0

Related:

  • No Related Posts

Custom Plugin & Attribute having issues with LDAP Lookup.

I need a solution

Hi All,

I’ve successfully integrated our proxy via ICAP which is feeding our Web Prevent Server.

I noticed the username was showing up as “local://sAMaccountname@domain.com”.  I added a new plugin successfully which outputs Username=sAMaccountname after parsing the ‘sender-email’ argument.  I then created a custom Attribute in our Employee field called “Username”.  We did not have this value prior.  My custom script successfully populates the new “Username” field.

My plugin Chain is as follows:

  1. Custom ICAP Username Parse
  2. LDAP

The exsting LDAP Plugin is as follows:

attr.Employee = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):displayName
attr.Employee Email = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):mail
attr.Employee FirstName = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):givenName
attr.Employee LastName = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):sn
attr.Employee Title = :(|(mail=$sender-email$)(sAMAccountName=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):title
attr.Employee Dept = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):department
attr.Employee Division = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):division
attr.Cost Center = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):ou
attr.TempManager = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):manager
attr.Supervisor First Name = :(distinguishedname=$TempManager$):givenName
attr.Supervisor Last Name = :(distinguishedname=$TempManager$):sn
attr.Supervisor Email = :(distinguishedname=$TempManager$):mail

When I generate a new ICAP event, DLP successfully executes my custom plugin and fills in the attribute “Username” with what is parsed as the AD sAMaccoutname.  All other fields are blank and from my understanding its due to my LDAP plugin missing the new field to lookup with.

1) I’ve tried to modify my LDAP lookup by adding (sAMAccountName=$Username$) but the lookup never works for Network Events and does not autopopulate or populate with a manual lookup.  I may be doing this incorrectly but I tried multiple ways.  I’m not sure if my order is maybe incorrect?  I need some guidance here.

2) After this change, Endpoint Incidents do not populate any custom attribute fields and when i click on “Lookup” an error message occurs with “Custom Attribute Lookup failed”.  I think this is due to my new custom attribute called “Username”

I think I’m missing something easy here but I’m not too sure at this point I’m getting confused.  Maybe how I modified my LDAP plugin? 

Any guidance at this point would be apperciated.

0

Related:

  • No Related Posts