Basecamp Export

From the list: Post-launch issues

✔ URGENT - Problem with IP Access

Morgan M. added this on Jun 30, 2021
Completed Jul 02, 2021 by Morgan M.

Assigned to

Harsh P.

Martin L.

Notes

Further to the video below, there is currently a problem with the Freshfields Bruckhaus Deringer LLP group account on ISLG. It is currently registering a high number of sessions from IP addresses outside the ranges specified in the account. These IP ranges were updated my

Marysia

last week, but I cannot identify any clerical errors in the ranges that would be causing this issue. Please resolve the following:

Ensure access is only getting granted to the authorized IP address ranges for the group.
Reassign any recorded sessions outside the authorized IP address ranges to other applicable group accounts (i.e., determine if these IP address that is associated with a session falls within the ranges of other group accounts and reassign the applicable sessions to those group accounts - sessions that do not fall within an applicable range can be discarded).

Please resolve ASAP. We are currently in renewal discussions with the client, and I do not want this to be something that jeopardizes the renewal.

Thanks,

Morgan

Problem with IP access in ISLG (29-Jun-21).mp4 8.03 MB • Download

Comments & Events

Harsh Parikh, Tech Lead

Morgan

and

Marysia

,

We checked the IP ranges for Freshfields Bruckhaus Deringer LLP group and found that as per following screen shot due to red mark ipv4 range this issue is occurred.

The range is start with 54.14.114.168 and end with 154.14.114.175. I assume this is typo mistake for ip 154.14.114.175. The start IP range should start with 154 digit or End IP range should start with 54 digit

iprange.png 109 KB • Download

Please check and confirm.

Jun 30, 2021 at 5:56 AM Notified 3 people

Morgan Maguire, CEO

Harsh

,

Great. Thanks for catching that.

Marysia

, I have turned off that IP address range. Could you please confirm what the correct range should be?

Martin

, can we do something about the usage data? I really don't want this to show up in the client's usage reports.

Thanks,

Morgan

Jun 30, 2021 at 1:02 PM Notified 3 people

Martin Laporte, CTO

Morgan

and

Marysia

: I am pretty sure that the correct IP begins with 154.*, because 154.* IP addresses originate from the U.K, whereas 54.* IP addresses are US-based.

Is it ok if we remove all usage data entries for that group from 6/23 until now? This would be the easiest way.

Thanks,
--Martin

Jun 30, 2021 at 1:09 PM Notified 3 people

Morgan Maguire, CEO

Martin

,

Ok. It may very well be a US-based IP, because Freshfields has several offices in the US, so I'll wait for

Marysia

to confirm the correct range.

I'd prefer a more precise correction of the data. This is a high volume account and there was probably legitimate usage that occurred during this period. Once

Marysia

confirms the correct range, could we please remove only the sessions that do not fall within an authorized range?

Thanks,

Morgan

Jun 30, 2021 at 2:24 PM Notified 3 people

Marysia Raptis

HI Morgan and Martin,

I confirm the range is 154.14.114.168 - 154.14.114.175

Marysia

Jun 30, 2021 at 3:33 PM Notified 3 people

Marysia Raptis

Also, have made the correction on their account.

Marysia

Jun 30, 2021 at 3:33 PM Notified 3 people

Morgan Maguire, CEO

Great. Thanks

Marysia

. Could you confirm exactly when the IP addresses were updated so that

Martin

can isolate what sessions data needs to be corrected.

Thanks,

Morgan

Jun 30, 2021 at 3:49 PM Notified 3 people

Marysia Raptis

June 23

Jun 30, 2021 at 3:53 PM Notified 3 people

Morgan Maguire, CEO

Ok. Thanks

Marysia

Martin

, could you please determine whether it's possible to cleanse session data between June 23 and June 30 of sessions where access came from IP address outside the authorized IP ranges.

Thanks,

Morgan

Jun 30, 2021 at 4:01 PM Notified 3 people

Marysia Raptis

Actually looks like I would have updated on 22 June and confirmed on 23rd.

Marysia

Jun 30, 2021 at 4:18 PM Notified 3 people

Martin Laporte, CTO

Morgan

, I will work on isolating the erroneous sessions today, but will wait tonight for

Harsh

before removing them since I want to make sure they are properly removed.

Jun 30, 2021 at 4:41 PM Notified 3 people

Morgan Maguire, CEO

Ok. Sounds good. Thanks

Martin

.

Note this can wait until Monday. I don't want to unduly interrupt your long weekend.

Morgan

Jun 30, 2021 at 5:13 PM Notified 3 people

Martin Laporte, CTO

Harsh

,

See attached spreadsheet for the list of erroneous sessions that should be deleted.

What I did to get there:

Collect list of IP ranges belonging to client (using SelectGroupIPRangesByGroupID stored proc)
Collect list of sessions linked to client (using SelectSessionDetailsForExport stored proc)
Brought the data into a spreadsheet and created a simple formula to validate each session from 6/22 until now.

Take a look at the "Sessions" tab, column R. The goal would be to remove any "FALSE" entries from the database.

Hopefully this spreadsheet will help you achieve that.

Thanks,
--Martin

SessionDetails_36.xlsm 299 KB • Download

Jun 30, 2021 at 6:55 PM Notified 3 people

Harsh Parikh, Tech Lead

Martin

,

As per your attached sheet, We have removed false session data entries from Freshfields Bruckhaus Deringer LLP ' s group.

Please check and confirm.

Jul 02, 2021 at 8:28 AM Notified 3 people

Martin Laporte, CTO

Harsh

,

I believe we are looking good now, as their June sessions count are back within normal ranges:

image.png 22.6 KB • Download

Morgan

: do you agree?

Thanks,
--Martin

Jul 02, 2021 at 11:28 AM Notified 3 people

Morgan Maguire, CEO

Look good,

Martin

and

Harsh

. Thank you. Marking to-do complete.

Morgan

Jul 02, 2021 at 4:23 PM Notified 3 people

Morgan Maguire completed this to-do.

Jul 02, 2021 at 4:23 PM