@jmoore said in How to hide a network printer:

Are you installing them as shared? If not they would have to know the IP or a hostname or something like that. I install ours as unshared, never had that happen.

These printers are available for install in Windows 10 and they are not shared by any workstation or server. They are simply printers with NIC card set for dhcp. Take them out of the box, plug in an ethernet cable, power them on and Windows 10 can see them and print to them.

Is there an easy way to prevent people from seeing a networked printer? If I setup a new printer on the network for three people to use, it doesn't take long before other user the Add Printer wizard in Windows 10 and are printing to it.

Is there a quick way to stop this?

@Pete-S said in How to start taking a company to Microsoft 365 based operations.:

@JasGot said in How to start taking a company to Microsoft 365 based operations.:

Any thoughts on what to think about and how to accomplish the goal?

Well, going "cloud based" is not a goal, that's a means to an end.
It would be interesting to know the goal. Not only interesting but crucial.

1. Their goal is to do away with any local (onsite) IT costs, including support. Not something I am in favor of, since we are an IT support company

2. because everyone says "cloud" is the way to go.

If a customer is asking to go "Cloud based" and they want to stay MS based. What would be you path for a customer who has standard server now.

My concerns are file access and file sharing. Very large graphics and video files, and lot of people all touching the same word and excel docs.

Any thoughts on what to think about and how to accomplish the goal?

Our customer doesn't want the city's bank account and routing info transported through e-mail. He was willing to do it if we could come up with a way that would guarantee it could not be read in transit.

He understands the sysadmins at each end can read it, and he understands that he has no control over what happens after it arrives at the recipient.

He, like me, has used systems that "appear" to provide a little more protection. ie; when my broker wants me to see a document, I get an e-mail that takes me to a web port. Once I log in, I can view the document.

The problem with this type of system is that a) we don't know if the employee at the state can visit any of these sites. b) we don't know if the employee at the state is willing to put forth the effort.

As for the PGP idea, we don't even know if the state employee is using an actual e-mail client.

So for know the customer really only has two options to alleviate his concerns: 1) continue sending by usps and wait a month or more for action, or 2) send an encrypted file as an attachment and HOPE the receiving mail server allows it, and HOPE the recipient will call and ask for the password.

With the possibility of little or no cooperation at the receiving end, the customer is basically SOL.

@JaredBusch Thanks. Not much more to it beyond what I thought. I was hoping someone would know of a solution that could work.

@JaredBusch said in Sending Secure E-Mail?:

Once you get that told to them, you can then to get to the reason for such a stupid request. Likely a misunderstanding of some compliance need.

Here's the request from the customer. It makes sense. But is also difficult to overcome. Especially with state workers who will likely say "Not our process, FU"

<snip>

I’m looking for options for secure email transmissions of sensitive data.

The dept is engaged in a grant program with the State Department of Environment…, which requires us to include our banking information on every reimbursement application.

Because the Governor has closed the State offices, forcing the staff to work from home, The Grant Office has directed us to submit our applications via email or take the risk of having our applications sit unreviewed for a month, since the staff only go to the office once each month to pick up their mail. Even then, they are scanning the documents and emailing them, via unsecured email, to other staff members.

I have refused to include the banking information on documentation submitted via email, opting instead to email “incomplete” documentation to the staff and mailing the “complete” documentation to State’s office.

Is there a relatively inexpensive option for secure email transmission available to protect our banking info?

I have a customer that needs to send e-mail to a company.
This customer does not want ANYONE other than the intended recipient to view the contents.

What are the options to do this, and what complexities do they impose?

I am aware of these methods and their problems:

1. send the info in an encrypted document that is attached
   1a) Some anti virus software will block encrypted attachments.
   1b) You still have to communicate the decryption password to the end user who is only available via e-mail.

2. Sites that allow you to send a document into their service/system and then the recipient has to go there to retrieve it
   2a) Recipient may refuse to go to a web site to retrieve an e-mail.
   2b) Recipient may not have web access with a browser.

Any other options? The key elements are 1) E-mail based and 2) cannot be read by anyone other than the recipient.

O365 has this built-in. Check Exact Data Match (EDM), and Data Loss Prevention (DLP).

You define what makes a document HIPAA restricted (EDM) (or for any other other reason if you wish, it does not have to be a HIPAA issue), and then you create a rule about how any document meeting that EDM can be viewed or distributed (DLP).

In a nut shell; Let's say you have documents with Social Security numbers, you create an EDM to identify SS #s in documents (this happens as you access them) and it flags them as having met the criteria for one of your EDM rules.

Then, your DLP rule can, for example, only allow the document to travel through email within your domain, or within a group (department, C level employees, etc). It can disallow the document from being downloaded or printed, etc.....

Have a look here: https://docs.microsoft.com/en-us/microsoft-365/compliance/create-custom-sensitive-information-types-with-exact-data-match-based-classification?view=o365-worldwide

@Skyetel said in Skyetel Postcards - What's Needed:

Both of these limitations are related to security concerns our developers had. We've seen people transmit information via SMS that they really shouldn't

As @scottalanmiller would say, that's an HR issue, not a technical issue.