Sign In

Marie Prokopets

Co-Founder & COO at Nira

Marie Prokopets is the Co-Founder and COO at Nira, a company dedicated to ensuring safe and secure collaboration for all users.

With a Bachelor's Degree in BS Business Management from Babson College and a Master's Degree in MA English Literature from The University of Connecticut, Marie brings a unique blend of business acumen and literary expertise to her roles.

Her professional journey includes founding and leading various ventures such as FYI and Up Advisors before co-founding Nira.

Marie also has a rich history with Diageo, where she held several key positions including Director Innovation & Strategy, Director Strategy & Tequila, and Director Commercial Planning & Strategy.

Prior to her time at Diageo, she honed her strategic skills at PricewaterhouseCoopers as a Senior Associate in both Strategy and Thought Leadership/Marketing.

Marie Prokopets champions data security and access control through Nira, which offers organizations real-time protection against unauthorized access to sensitive company information.

Highlights

Mar 21 · linkedin

I’m going to predict the future here so bear with me…

You’ve deployed Copilot for Microsoft 365 and the information floodgates have opened.

Great!

Except… now employees have access to information in a more efficient manner than ever. And not just the information they should be able to see. It’s also the things they really shouldn’t have access to.

Like that confidential board deck that accidentally was shared with the entire company. Before Copilot, employees would have to search for the deck (or get a link), find it, then read it to discover information they shouldn’t be able to see.

Now, this information is as simple as asking a question to the Copilot and getting the answer.

For example, an employee could ask for a list of all the files and chats that referenced company strategy. Only to find confidential documents and Teams Channels they didn’t even know existed.

Here’s what’s happening. Microsoft Copilot is indexing the Microsoft 365 documents, emails, calendars, chats, contacts, and more that each and every employee has access to. And then, it’s allowing them to ask questions across everything they have access to.

This means that all of a sudden those problems of oversharing, inadequate permissions, insider risks, and privacy are now amplified.

I’ve been thinking about this a lot, and hearing it from CIOs and CISOs too.

To help organizations understand these risks and mitigate them prior to deploying Copilot for Microsoft 365, I’ve written a guide. Link is in the first comment below. Would love to hear what you think.

Sep 7 · linkedin

What Chrome profile do you use while working?

At Nira, we've learned that it's way more common than you'd think for employees to use their personal Chrome profiles when they're working, which can create a number of security risks and headaches.

For example, in Cisco's 2022 breach, company systems were breached because an employee stored company passwords on their personal Chrome profile.

This practice is actually really, really common.

People don't realize that using their personal Chrome profile can create security risks for the company. One of those risks that we discovered is when employees accidentally create company documents using their personal accounts. They’re in their personal Chrome profile, they go to make a new document, and get to work. They think they are working using their company email, put a bunch of confidential information into the document, and then they share it with other people at the company. Except it’s not their work email - it’s actually their personal email account.

We surveyed over 300 people about this exact issue, and when we asked “Have you ever accidentally created a document for work using your personal email account?” 51% of people said they had. This practice is much more common than I originally thought.

This same issue can happen when company documents with public links are shared where anyone on the Internet can view them. The employee accidentally opens these documents on their personal Chrome profile, and now those company documents are accessible from their personal Google Drive instance.

Typically this employee behavior is one that IT teams never find out about. This is behavior that we surface with Nira. Our customers are able to see which documents were shared with employee's company accounts, but created by employee personal accounts.

Personal account usage for work is a problem, not only because of passwords that are put at risk, but because personal accounts don’t normally have as robust of security procedures, putting any confidential information they have access to in documents at risk too.

Is this something you’ve ever thought about or done yourself accidentally? I’m curious, leave a comment or message me.

Marie Prokopets
Add to my network

Location

San Francisco, California, United States