Row 56822

Row ID: 56822 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 56822 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

Actually, the IT admin functionality is really well fleshed out, so is the account level security, and zero data is transmitted or processed remotely. And yes, this will be easy to technically validate. And the way they are stating they encrypt the data makes it reek strongly of Pluton enclaves, VBS, and EFS-style key management (though more robustly implemented in hardware). Reset the account's password through ADUC or another type of password reset tool? All that data is now just cryptographic trash, etc.

The upside to this is if it does happen, it's easy to catch and prove, and a hefty $9.3 billion GDPR fine would be just the beginning of Microsoft's worries. Shareholder lawsuits because of the loss of profits from the fine, other national/international regulators chewing at the bit, etc....

Really, the way they implemented it means that we'll (An F100 defense contractor) probably be able to allow its usage unlike "regular" copilot when the hardware required for it to function becomes more widespread. Sure, we'll have a restricted list of applications and resources that it can't record when in use, but for "general" stuff it'll likely be enabled because there's no cloud processing, unlike say, grammarly or copilot, which are forbidden.

The whole implementation also reeks to me of "we designed this explicitly to be GDPR compliant" while also "make it borderline impossible to extract the data in nefarious ways" as well as having a rolling delete, which in a cryptographic sense means all the oldest data dies off. And with the configurable timeline, retention policies aren't an issue either.

From a management perspective, it's not a nightmare at all. Both in configuration and data sovereignty/privacy perspectives.

It's not as "bad" as telemetry is, but even that set to the basic (not even the "security only") level was deemed not a data leak risk after extensive testing and evaluation by multiple agencies and our own organizational security teams.

Copilot itself, and web search results in the start menu, however, were deemed potential risks.

FieldValue
text Actually, the IT admin functionality is really well fleshed out, so is the account level security, and zero data is transmitted or processed remotely. And yes, this will be easy to technically validate. And the way they are stating they encrypt the data makes it reek strongly of Pluton enclaves, VBS, and EFS-style key management (though more robustly implemented in hardware). Reset the account's password through ADUC or another type of password reset tool? All that data is now just cryptographic…
label r/technology
dataType comment
communityName r/technology
datetime 2024-05-23
username_encoded Z0FBQUFBQm5Lak1XLTBZbGRVTm5XYXo1UXRESEE0ZjBuSGhDVl9KbzJyS2lfazJ1eFlUXzdlWWVQU1M5RVd1T2ZweUtIVFpGRmJ1OFBKTXZCSVVPLXRKZlJHVzBQbmRobXc9PQ==
url_encoded Z0FBQUFBQm5Lak9tWHVZWjFteVNmTHB2U0ZpUDVFTlpuZlNERFhGTDFUTVRLbzZuZDUzN2ctMk5IbDZyTTZmQ1U0Vl91bnEtT2ZhYVJ5RE1oUnYwcl9DeTlYYVotQ0F3Tk9xS3AydUtEX2FxbEt3M040d2JOX2xMalJmd25tSk9fLXJMdDdBQXQ2RE9LZkpWQnVHTVBHWE11RjYwekZnY1lVNmVDclg3eURSamhreFUzQTVUX2d5T3dpdlNsRUtpN3JYUFdGZnpmeDJKNnJ0bklyeVN1TmdWX2hteWtKZzdpZz09

Raw Record

{
  "text": "Actually, the IT admin functionality is really well fleshed out, so is the account level security, and zero data is transmitted or processed remotely. And yes, this will be easy to technically validate. And the way they are stating they encrypt the data makes it reek strongly of Pluton enclaves, VBS, and EFS-style key management (though more robustly implemented in hardware). Reset the account's password through ADUC or another type of password reset tool? All that data is now just cryptographic trash, etc.\n\nThe upside to this is if it does happen, it's easy to catch and prove, and a hefty $9.3 billion GDPR fine would be just the beginning of Microsoft's worries. Shareholder lawsuits because of the loss of profits from the fine, other national/international regulators chewing at the bit, etc....\n\nReally, the way they implemented it means that we'll (An F100 defense contractor) probably be able to allow its usage unlike \"regular\" copilot when the hardware required for it to function becomes more widespread. Sure, we'll have a restricted list of applications and resources that it can't record when in use, but for \"general\" stuff it'll likely be enabled because there's no cloud processing, unlike say, grammarly or copilot, which are forbidden.\n\n  \nThe whole implementation also reeks to me of \"we designed this explicitly to be GDPR compliant\" while also \"make it borderline impossible to extract the data in nefarious ways\" as well as having a rolling delete, which in a cryptographic sense means all the oldest data dies off. And with the configurable timeline, retention policies aren't an issue either.\n\n  \nFrom a management perspective, it's not a nightmare at all. Both in configuration and data sovereignty/privacy perspectives.\n\n  \nIt's not as \"bad\" as telemetry is, but even that set to the basic (not even the \"security only\") level was deemed not a data leak risk after extensive testing and evaluation by multiple agencies and our own organizational security teams. \n\n  \nCopilot itself, and web search results in the start menu, however, were deemed potential risks.",
  "label": "r/technology",
  "dataType": "comment",
  "communityName": "r/technology",
  "datetime": "2024-05-23",
  "username_encoded": "Z0FBQUFBQm5Lak1XLTBZbGRVTm5XYXo1UXRESEE0ZjBuSGhDVl9KbzJyS2lfazJ1eFlUXzdlWWVQU1M5RVd1T2ZweUtIVFpGRmJ1OFBKTXZCSVVPLXRKZlJHVzBQbmRobXc9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9tWHVZWjFteVNmTHB2U0ZpUDVFTlpuZlNERFhGTDFUTVRLbzZuZDUzN2ctMk5IbDZyTTZmQ1U0Vl91bnEtT2ZhYVJ5RE1oUnYwcl9DeTlYYVotQ0F3Tk9xS3AydUtEX2FxbEt3M040d2JOX2xMalJmd25tSk9fLXJMdDdBQXQ2RE9LZkpWQnVHTVBHWE11RjYwekZnY1lVNmVDclg3eURSamhreFUzQTVUX2d5T3dpdlNsRUtpN3JYUFdGZnpmeDJKNnJ0bklyeVN1TmdWX2hteWtKZzdpZz09"
}
Explore Dataset Explore Row

Entry Information