Yes, and since Active Directory is largely based on Kerberos and LDAP, we must assume that MIT and everyone involved in LDAP/X.500 have no idea what is going on either. Because some anonymous asshat said so. Please share your text file based solution to managing 100K users and all of their associated equipment, we'll wait.
1. Fog Machines. You'll need to generate enough fog to completely eliminate visibility. Run the fog juice through the muffler, then route the exhaust into the passenger cabin, and you are good to go.
2. Anesthetics. Pump some "anesthizine gas" into the cabin, and knock everyone out. See Star Trek: TNG for the specifics.
3. Blinding Lights. Deploy lights so bright that the burn out any camera sensors and/or retinas. Optionally, provide shielding visors. See Star Trek: TOS "Operation: Annihilate!" for the specifics.
There was a specific policy, covering all departments, that information like that was not to be transmitted in the clear, and even when transmitted encrypted, the applications were to be registered with the security department. Those applications would be subject to increased scrutiny, particular for extrusions and data leakage.
As the device could only catch unencrypted transmissions, those were all, by definition, in violation of policy.
Years ago I worked for a government IT department. A vendor wanted us to try out a product. The device plugs directly into the Internet connection, and monitors every packet, in real time, looking for strings matching an array of string that you provide. We ran queries against our internal databases, and compiled a list of SSNs and CCNs. The vendor programmed that data into their device, which from what I can tell used an FPGA to perform deep packet inspections.
We expected that we might see maybe an email every week or two where someone accidentally sent that kind of information.
First hit occurred 12 seconds after turning the device on.
Etc. Etc. Etc.
Within an hour, we had overrun the quota on the network directory where we were logging this data.
We found hundreds of separate systems that were transmitting this kind of data without authorization. We were planning a massive internal sweep to find and fix them all, when the following came down from management:
Shut it down. Remove the device. Destroy all logs, emails, EVERYTHING. Offer the vendor a payment in return for signing an NDA. All employees required to sign secrecy docs (unenforceable at that level of govt, but still.)
I believe this is how the acronym SNAFU came into existence.
Almost every Windows corporate PC has been running a logon.bat script at least once a day for the last twenty years.
Now every logon.bat is different, but if we are playing loose with the semantics...
my god... it's full of idiots. and trolls. and closet cases...
It really depends on the buffer size, which tends to be brain specific.
I assume you mean this Rick Shaw:
Weekend Savings Time: Friday @ 4 PM, skip ahead to 5 and leave work early. Monday @ 7 AM, set the clock an hour and sleep in.
Clearly, the only way we can be sure is to disassemble Bruce Schneier. Glove up.
If you don't think that Oreos are just as addictive as cocaine, then you clearly aren't snorting/freebasing/mainlining them properly.
Funny how the most secure organization in the world let Snowden just walk out the door with everything on a flash drive.
From the website:
'The current Demo CD is based on the eComStation 1.2 product and does not reflect the current state of the eComStation 2.0 product."
"the equivalent of studying GLORIOUS EAGLES." get your imagery straight.
I'd be fine if the manufacturers and carriers would just make their bloatware an optional "feature" that users could take or leave. Like AT&T Maps; it's $10/month, the one time I used it was by accident because I confused it for Google Maps.