A group of ex-NSA and Amazon engineers are building a ‘GitHub for data’
techcrunch.com
techcrunch.com
I said, in good faith, that I would consider his product if I could inspect the running system and the code.
He said several things: 1) the NSA never did anything illegal 2) the software was too large to audit 3) it was an insult to his employment in the NSA that I was even asking these questions.
Then he hung up.
Who is it?
That part's probably true.
Try to audit something like OpenSSL.
Edit: more importantly, the FIPS version of OpenSSL was vulnerable to HeartBleed.
https://www.engadget.com/2019/06/13/yubico-recalls-governmen...
Who did you work for? This appears to be a 180deg misunderstanding of the 5 Eyes agreement. GCHQ is not allowed to spy on Americans.
"In partnership with the British agency known as Government Communications Headquarters, or GCHQ, the N.S.A. has apparently taken advantage of the vast amounts of data stored in and traveling among global data centers, which run all modern online computing, according to a report Wednesday by The Washington Post. N.S.A. collection activities abroad face fewer legal restrictions and less oversight than its actions in the United States."
Note there's a fair amount of speculation on the specific details of how and what data is collected and shared.
> "pushed back against the notion that it was collecting abroad to “get around” legal limits imposed by domestic surveillance laws"
https://www.zdnet.com/article/thatcher-ordered-echelon-surve... > Ex-spy Mike Frost told the CBS 60 Minutes programme that Thatcher had ordered surveillance on two cabinet colleagues according to excerpts released on Thursday. The allegation comes in the same week that a European Parliament report said Echelon, a surveillance system run by the United States, Canada, Britain, Australia and New Zealand, was used for industrial espionage.
I can't recall the details - Ill have to go look it up again, but apparently Israel gets more data than any of the others, IIRC.
When someone says something about mysterious unseen evil activities and Israel it raises my conspiracy theory detector to yellow alert
Since when do spy agencies avoid doing things just because they're "not allowed" to do them? An activity being disallowed only means that they'll avoid telling people that they're doing it.
This is how the misspellings in Nigerian Prince emails market to the "right" customers.
Okay... but even if it was legal that doesn't mean what they did is "right". There's a big difference.
I don't really find that rude. A cloud customer certainly can go to a cloud provider, say "you know, it's possible you have rogue internal actors, I've read articles that said you've fired SREs before who snooped on user data, can I see your audits that show you deal with insider risk properly?"
Oren Falkowitz CEO and Co-founder Oren Falkowitz co-founded Area 1 Security to discover and eliminate targeted phishing attacks before they cause damage to organizations. Previously, he held senior positions at the National Security Agency (NSA) and United States Cyber Command (USCYBERCOM), where he focused on Computer Network Operations & Big Data. That’s where he realized the immense need for preemptive cybersecurity.
What issues?
Honestly, why are you defending someone who believes that??
/s
This post could turn into +5 informative if names and contact details were added for this unidentified "ex-NSA guy" and the "security software."
As-is, this is post is becoming popular because people are replying with random experiences and hate they have for NSA and insecure systems. But instead it could be helpful by damaging the reputation of a specific person that is peddling insecure systems.
This is why I browse with -5 insightful.
This is simply not true.
So, what do you get out of it compared to simply training models as a service for people? Almost nothing useful. All you get are:
- Much worse privacy guarantees. (People selling synthetic data love to talk about improved privacy, but it's actually the reverse. The privacy guarantees for synthetic data are much, much worse than selling direct models to people.)
- Much worse model performance. See the previous notes about how a synthetic data generating procedure must have already solved the problem at hand.
- A much more complicated setup with much more expensive model training. Training generative models is hard and requires a lot of data and compute due to the difficulty in learning such a complex outcome space. This can easily cost 100-1000x as much as simply training a straightforward xgboost model.
Other examples I could think of fall in the category the top comment is referring to.
1. Already doing that, in which case it's already the superior model.
or
2. Not doing that correctly, in which case the synthetic data output is equally poor.
At the risk of digressing from TFA, Candes’ knockoffs, for instance, are an example of a (theoretically) successful use of synthetic data for model robustness. Still need original data, of course.
Basically, the broader point is that you don’t need to solve the full problem of joint likelihood estimation to use generative models effectively, e.g., GANs are another example.
You can see some of my work here:
https://medium.com/capital-one-tech/why-you-dont-necessarily...
The reality is, you can guarantee certain values are not passed. That’s fairly easy, what you can’t do is block general trends easily in synthetic data - else the model can’t learn. So you have to be willing to accept that “leakage” when using synthetic data.
If you accept that leakage, then you can actually improve model performance in some domains. See ubers architecture search blog, there’s a lot of material (also from Uber) showing this.
Regarding cost of training, yes model training costs could increase. Although, I’d suggest much much less than 10x more like 50% or something. Is that worth it for privacy?
Guaranteeing that certain values are not passed is both useless and trivial. I can easily satisfy that by simply adding 0.1 and a space character to all values in my dataset even though that doesn't remove any of the sensitive data.
Nonsense. There's a fundamental requirement that for a model to have utility, it must have access to relevant data. If you truly find a leak-proof way to block certain values (which is borderline impossible in itself), then you make the model significantly weaker or outright useless if those values aren't uniformly distributed across the input domain.
And if you do have leakage (and you almost certainly do), then direct re-identification becomes a trivial problem and we're back to square one.
Synthetic data generated from statistical analysis of real data is either worthless or leaky. One of those two conditions is formally guaranteed to be true.
GP is correct that a viable synthetic data generator basically has to have already solved your problem for you, and in that sense it just becomes your model which is trained on real data. Training an additional model on top of that model doesn't add any privacy or mitigate reidentification.
I'm being pedantic by posting this though, because their approach involved learning the synthetic data generator simultaneously with the classifier/whatever that you're training. That is not relevant for a static synthetic data source.
The idea that training on synthetic data is a “charade” misunderstands the usefulness of having realistic, “drop in compatible” data that works with your existing code or models.
The ideas of training models as a service and also of working directly with synthetic data generators to “extract“ from them are great but incompatible with (a) the complexity of real world DS workflows in regulated industries and (b) data scientists current code / workflows / techniques.
If I’m a bank, I’m not going to give you my fraud rules and you’re not going to solve my problems with xgboost. Access to models is just as locked down as access to data.
This is why it’s useful having an intermediary. Like ... a generative model that you can train where the data is and then copy over to where the modelling is happening.
As an intermediary like you describe is far different than "I don't have enough real data for what I want to do", for example.
Assuming the problem at hand is analyzing the data.
I don't know enough about what they're building to understand what use cases they have in mind. (Their blog says "developing new features or exploring insights", which is a bit vague. See https://medium.com/gretel-ai/gretel-readme-fd0c4eff8a09 .)
But if this allows people to take their production database, run a command, and generate fake data they can run integration tests against, then that's not analyzing the data. It's making it easier to run tests in an environment that is as close as possible to production, because data is part of an environment.
Aside from that, I'd argue that some kinds of analysis may even still be possible. Let's say you have an e-commerce site, with one database table for user accounts and another table for shipping addresses. And let's guess that Gretel anonymizes this data by creating a user table with different usernames and an address table with made-up shipping addresses, but the overall structure is isomorphic: for every row in real data, there is a corresponding row in fake data, just with different values in it. And the (synthetic) keys aren't private (they data you generated, not collected from the user), so they can be preserved. Then you can, on the fake data, run a query and find out what percentage of users have given a shipping address.
Of course it's just a guess that that's what they're aiming to do since so little detail is available. It's entirely possible that what I described isn't what they're planning to do. Maybe it doesn't sufficiently protect privacy.
But the point is, until we know what they're building, I don't know if we can conclude that people should run away.
I've heard this group is pretty good, and they seem to be proud enough of their synthetic data to publish papers on it:
https://ai.googleblog.com/2020/02/generating-diverse-synthet...
Illuminate me, why are they wrong?
Generative models do not necessarily know P(X,Y), often they simply give samples of (X,Y) using some map
G: Q -> (X,Y); Q~N(0,1)
Actually getting P(X,Y) would mean inverting G, which is not always possible (although there are some invertible GANs).
Computing P(X) is often computationally intractable as tracing out variables can be arbitrarily expensive.
Example: Training an image upscaling algorithm by feeding it downscaled images. In this case you don't even need to train a generative model (the algorithm is known), but it should illustrate that the generative task can be extremely easy compared to the target task. You can't just handwave that away with "just divide by P(X)".
I wish these folks luck! Perhaps things have changed; we were part of a flock of 5 or 10 similar projects and I'm pretty sure the only one still around today is Kaggle.
I happened to have a long discussion on the topic of data businesses last night with a friend. We brainstormed datasets that would be a combination of hard/expensive to obtain while also having resell ability to thousands of customers who would be willing to pay a high value for them. I don't want to get involved in datasets that are easy to obtain (too many competitors, no bar to entry) or datasets specific to a particular company (too much dependence on a small set of customers, cost of acquiring new customers also includes cost of acquiring data, no economy of scale).
It's easy to start with the tech problem: how to collect, clean and analyze data. But reasoning backwards from the business side is much more difficult. Expensive data I can sell once feels easy. Cheap data I can sell frequently feels like a race to the bottom. Expensive data I can re-sell 1000s of times to a niche audience feels like a perfect middle ground ... I just can't think of any examples.
Isn't it more like "nearly always"? It's pretty hard to find examples of things that haven't been tried multiple times before in some variant. You can argue if it was timing or execution that worked "this time" of course, but almost nothing happens in isolation.
Maybe? Hard to see past survivorship bias. My intuition says some ideas will never see their time. Hard to quantify how often that is the case as a percentage of all ideas.
Lots of ideas are just bad. The ones that work out though, are very rarely original I think (in this context, at least).
- How many truckloads of widgets did the widget company ship out of Warehouse A compared to Warehouse B in 2019 vs 2018.
- What is the purchase ratio of titanium to steel for Company X over the past 5 years?
This type of data is valuable to seek out emerging trends, risk minimization, stock analysis, etc. Very hard to find legitimate data on your own.
Some key contributing factors: multiple stakeholders & consent/approval issues, legal & technical constraints on access, depending on the application labeling may only be possible using very expensive experts. Lot's of human interaction.
Commercial viability of doing so for profit is a different issue, but I see that's the other part of your original comment. It's not an obvious answer, partially because there are a lot of different scenarios within that blanket "medical imaging", and what the putative customer might want to do with it.
Basically, identifying companies that are doing well / expanding by how big the space is they leased. This sort of data is apparently very hard to get, but gives users a competitive advantage.
What other markets for data are similar? In general, data that leads to prospect generation is desirable because sales agents are willing to spend money to make money. Are there any other markets like that?
I'm curious how they figure out how much to charge companies for this data? And also how they stop real estate insiders from gaining access without sharing new data?
SMART on FHIR is a newish standard for medical applications that is getting a HUGE push from large companies like Cerner, Epic, along with all the tech giants. Hospitals are itching for more FHIR apps that can integrate directly into their Electronic Health Record system (and web apps be delivered directly on a doctor's web portal within the hospital's IT system).
So that might be a good place to start poking around...
Here's a good brief overview: https://healthtechmagazine.net/article/2018/10/everything-yo...
My first thought is specific business industry analysis data. I've often been an hour into an online deep-dive only to hit a paywall related to this. However, I'd think it would be hard to acquire the valuable aspects of this data without some kind of insider access (compared to web scraping, creative api mining, etc).
New data source needs seem to popup out of nowhere - what about building a platform that would facilitate the "collect, clean and analyze data" aspect of this for non-technical business owners?
It matches roughly the kind of data I was talking about. It is expensive to generate since you have to pay a researcher some amount of money to write the report. The resultant report generally can be re-sold multiple times.
My problem with this kind of data is that you will be competing against AIs pretty soon which will drive the cost to generate such reports down. And the price you can charge per report will be tied to how good a report you are capable of generating. It is also a saturated market already so the real play is driving the cost of generation down, not what I want.
In other words, instead of being a Gartner, focus on being a Crunchbase. That way, you can sell to both the end users of these insights (the companies in these industries) as well as the market research companies, themselves.
One of the problems with this is how custom each data set for each client would be. My mind has been on this topic since the a16z article on "The new business of AI ..." [1] which was posted to HN in the last couple of days. The key idea is the question of how to decouple the process of collecting, cleaning and analyzing data from the process of acquiring customers for that data, and not how to solve the problem of collecting, cleaning and analyzing data. Developers want to solve the technical challenge (how to build the processes) but not the business challenge (how to find customers willing to buy the resultant data).
I do believe there is a market for start-ups to partner with exiting companies to help them wrangle their data. It just isn't the market I'm thinking of.
1. https://a16z.com/2020/02/16/the-new-business-of-ai-and-how-i...
A few questions: What types of businesses would be "customers of that data"? Brainstorming all potential customers separated by industry would be a good start. Are there any "data purchasing" trends you've seen lately?
That is the exact question! That is the wall we hit. If I could consistently answer that question then there is a business to be had.
Who is willing to pay for that kind of data? I actually considered getting together a larger group of friends to do that exact brainstorm. But even then I'm not sure it is such an easy question to answer.
Also a bit funny you called it a gold-mine business. I called data that meets that criteria Goldilocks data.
Of course, if you can sell it to one person, they can just pass it off to others, so this will quickly turn into a DRM business profiting off tragedy. Probably not a good idea.
It's annotation. That is a workforce problem. You want to automate contracts? You need attorneys. You want to automate radiology? You need radiologists. You want to automate driving? You need drivers.
This makes ML less like a SaaS business, more like a mining business. There's tons, literally tons, of data/ore for any interesting problem. That's why it's an interesting problem. There are buyers of iron, gold, and marble. There are buyers of driverless cars, physician decision support systems, and contract automation solutions. But recovering the data from the mine (digitization) and enriching it (annotation) cost money. So much that the market variation may make it lucrative at some times and not others. If you are near peak employment, the value of a model goes up, but the cost of annotators is high also.
I'm not sure how finance guys capture that problem: how do you make a profit when there's high demand on both sides at one time, and low demand on both sides at other times? I submit that when both sides are low is the time to do annotation, and the time with both sides are high is the time to sell models.
But then you need an investor who can ride out the market.
I have started and failed at several endeavors that were too early for the market, investors, hype...
And when recognized as good ideas, I was crushed by those with more resources to execute than I...
I feel a bit numb over my career arc at this point.
> This so-called “synthetic data” is essentially artificial data that looks and works just like regular sensitive user data.
So its like Lorem Ipsum generator for data? Whats the use case here besides building apps with sample data? Notwithstanding potential privacy concerns, How am I confident that this is realistic if you literally say its generated?
General data repository for research with some mechanism to ensure cleanliness or integrity sounds much more useful to me.
Say you use regular expressions to extract sensitive data from standardized, but numerously varied, form documents. The pieces of information extracted are very common classes of data: first name, last name, dates, physical locations.
During the extraction process you can save the complement of the extraction (the "leftovers") and insert generated data at the extraction points. Also, because you've extracted the actual sensitive data, you can exclude that from the set of values used for generation, if it's practical.
Sometimes people get caught up in the math and theory that they fail to see the practical solutions.
G: Q -> (X,Y)
where Q is some prior from which you are sampling. If they are not invertible then you straight up cannot get P(X,Y) out of the generator. Even if it is invertible getting P(X) requires integrating out the Y which might be infeasible (since the model is not integrable and is sufficiently fast changing that you need very, very many samples).
Which is part of the reason for the high failure rate.
Good governance and data access for health data is a very hard problem. Good labeling is also hard/expensive in this space.
So there is an incentive for people wanting to do ML/AI without solving above to try any kind of shortcut they can think of. This incentive doesn't help solve any real problems.
The classic solution to "too little data" is use a simpler and/or less discriminating model. It's still the only one with a good track record.
Kind of, transfer learning is an important tool that people should use more.
People already use it quite a lot. More importantly they misuse it a lot. I'd be less concerned with increasing the usage, and more concerned that the people using it understand the implications and trade offs.
Of course, that would still be hairy as you'd have to ensure your ML still performed on real data sets. All the clean data would do is allow you to write unit tests of sorts for your ML with more confidence than the all-too-common unclean real data.
No idea, just making stuff up. Interesting thought.
Just because it may have some drop in utility today from real data, there are all sorts of scenarios where that’s outweighed by speed and ease of working with fake data rather that tied up in red tape real data.
See for example: https://hazy.com/blog/2019/12/09/data-science-on-test-data
Also, synthetic data can be augmented, rebalanced etc. Which is why in future it may well perform better than real data for data science work.
For example, think about this person does not exist and then apply that to business data.
Disclosure: Hazy cofounder. We’ve been doing smart synthetic data for a few years now.
Also this for a practical use of synthetic data.
There are a few areas of current practice that have this feature: a) the arguments & evidence for it being worse are pretty simple and b) the arguments & evidence for potential benefits are either weak or very convoluted. This is never a good sign.
I think this happens mostly because the reasons these things are being done are for the most part not technical, but the technically oriented people involved don't like to think about that way, and would rather talk about technical solutions - but that is operating at the wrong data.
The business & cost cases behind not doing this "right" in some abstract sense are pretty clear too, though. I wish more people would just be clear about this, and spend less effort obfuscating and more in clearly quantifying the cost of these workarounds.
Any time you hear someone starting off by saying things like "we don't really need good labels", "this synthetic data will be better, actually", "we'll use transfer from X because it's already done most of the work", etc., well what follows is quite likely to be good fertilizer.
Note, I'm not saying these approaches don't have value, just that there is an awful lot of magical thinking going on around it, and a lot of failures due to that.
I totally agree that the business need is the driver and that people miss the imperatives if they look at it purely from a technical or mathematical lens.
In a sense, synthetic data is the least bad actually viable solution. The democracy of privacy / data agility :p
My issue is not that people just miss the imperatives, but that they also misapply effort because of it. Accept there is a cost and try and quantify the impact. Make intelligent risk management decisions based on that. Sometimes that decision is "this is unlikely to work, what else can we do".
That's what I'm guessing. It could be used for AI stuff but also other useful datasets that are closed off or require special access.
I'm guessing a lot of defence contractors and other heavily regulated industries (ie, healthcare, insurance, pharma, etc) have similar problems in the dev process of not having access to real data. This was the leading pitch:
>> Data is valuable for helping developers and engineers to build new features and better innovate.
That's just my guess though.
It's a technique we've used in the DoD a long time and it works ok when everything is perfect. There are a lot of boundary problems like being able to troubleshoot bad data if you are doing your initial analysis with the transformed data, having DS's actually grok the problem-set since it's abstracted etc...
Edit: It's worth noting that this is a technical solution to a policy/legal roadblock. As organizations mature into better data governance, they are pushing more fundamental changes to governance that gets at these problems where solutions like this will no longer be necessary. For example, hiring data scientists into the groups that have access to the raw data (in our case hiring data scientists and giving them security clearances).
The use cases that this addresses are ones where you cannot train models in the same system/space/network as where the data exists.
This is a particularly good question since it's recently been shown that even neural nets trained on real data often pick up substantial, predictable dataset biases.
Practically every single-dataset-trained CNN seems to pick up stylistic quirks in the photos or labels it's trained on. The most visible result is that the CNNs perform better on same-dataset test examples than they do in the wild, sometimes vastly better. More startlingly, it's possible to work backwards from this: the training source of a "finished" CNN can be discerned by looking for certain types of error, and adversarial examples can be predictably constructed based on training source.
Tagged imagesets undoubtedly have stronger and harder-to-remove 'fingerprints' than text data like addresses, but I'd be shocked if the problem was nonexistent for text. My first reaction to "synthetic sensitive user data" for ML is to worry about winding up with systematic errors coming from the generation scheme.
Our company is actually building Git for Data and Github for Data. We have an open source database called Dolt which combines the commit graph of git with the relational tables and SQL of MySQL:
https://github.com/liquidata-inc/dolt/
Then we have a DoltHub, which is Github for data:
Dolt lets you version, branch, and merge your dataset so that you can collaborate on it with others. Dolthub lets you share your dataset with the world, submit PRs, fork other people's repos, and lots of other analogous features to Github.
> A mental retard who is clueless not only about current events, but also has the IQ level of a rock. "Dolt" may be the most sophisticated insult in the English language. Dolts commonly populate such stereotypes as jocks, nerds, fruits, bookworms, and dorks.
SDR captures PCAPs Microphone captures Public tax records Road data Flight plans etc...
Just anything and everything on one service with the limitation that it's all open data. No license agreements or legal restrictions.
It would probably never fly, but it would be amazing.
And this company isn't really even aping GitHub given that they are generating the content too.
Although having said then when you say data to me, I do imagine some level of immutability. Logging scientific results using git would be pretty good if required, in the sense that there is a habit to just use folders and text files which is fine at the time but is really really hard to take over sometimes (Like code written by scientists with their single-letter variable names and hatred of functions, in my experience of Fortran - yuck)
At the end of the day, the dragnet surveillance decisions came from the highest levels of the Bush and Obama administrations, not the boots on the ground.
For example, if someone got a job on a shark finning boat maintaining the knives, they're still complicit in shark finning even if they're never touched or seen a shark in their life.
And even if their actual role was spying on and helping detain Americans for arbitrary reasons, nobody's going to slap that on their resume. They'd say they were a data aggregating administrative officer.
"Historically, the plea of superior orders has been used both before and after the Nuremberg Trials, with a notable lack of consistency in various rulings."
Why should we respect those that spy on us? Would you expect Germans respect the Stasi?
I think that has a lot to do about which social circles you move in. If I saw NSA on a CV I would throw it in the trash.
True, but the "boots on the ground" are OK with it enough to go along with it. Their hands may not be quite as dirty, but they certainly aren't clean.
"NSA staff used spy tools on spouses, ex-lovers"
https://www.reuters.com/article/us-usa-surveillance-watchdog...
Optic Nerve ("GCHQ" in title is misleading because the NSA played a very enthusiastic helping role in it):
https://en.wikipedia.org/wiki/Optic_Nerve_(GCHQ)
ECHELON:
https://en.wikipedia.org/wiki/ECHELON
There's so much they're responsible for that it seems like it'd be excessive to post all of them, and HN has a character limit, anyway. Even the most well-known ones would fill a couple of comments.
However, adtech companies damage everyone, and fairly significantly. eg concentration problems, addictive behaviours, etc.
That's literally "human race" level damage.
Doesn't seem like a lesser thing to me. :/
They, for years until it was leaked, "targeted" every phone call in the United States:
https://gizmodo.com/this-government-phone-tapping-thing-just...
And 125,000,000,000 globally, along with almost a hundred billion internet requests per month in a time when the Internet was much smaller, years ago, under a program that hasn't stopped:
https://en.wikipedia.org/wiki/Boundless_Informant
This definitely damages everyone, and I think more fundamentally than adtech companies. You can escape adtech companies: use different websites, install an adblocker, block trackers, whatever. There's no obvious way outside of strong encryption and hermitry to avoid NSA getting its paws on every single public or private communication you ever make, given their record. When privacy doesn't and cannot exist, human behavior changes deeply. I think it's the greater of two evils.
Adtech companies definitely aren't good, by any stretch, but I think it's the difference between Ghengis Khan and a common killer: sure, they both want to kill you, but the scale and the level of cruelty is much different.
If I ever am, NSA in the history is a solid red flag. Be nice or go home. Willingness to participate in all that makes me wonder about your character.
Facebook almost as much, depending on when and for how long. The more recent, or longer sustained stay, again. Be nice or go home.
Google a little bit more reasonable, especially if only ever on the app/project side vs main service.
Adtech experience, I'd have to ask if they'd washed their minds out and won't even consider any of those tactics ever again... on second thought, almost as bad a flag as NSA crap.
Even if it's only a small drop of resistance in an ocean of "yeah, ok, whatever", I feel like we should signal that certain behaviors _against_ your fellow humans are poorly regarded.
Edit: figured this would get downvotes, ah well.
Participate in what? The NSA does many different things and has many different positions. Would you hold NSA's janitors responsible as well?
Obviously, the higher up the ladder a person, the stronger this effect is. However, that someone is willing to work in any capacity at an organization that behaves badly (in my view) says something about that person.
It is also open source and written in python. https://github.com/quiltdata/quilt
https://medium.com/capital-one-tech/why-you-dont-necessarily...
The market opportunity is very large, but also insanely difficult to tap.
For one, you have an uphill battle on trust. Customers have to trust your data is secure, and btw it’ll never be 100% secure by many standards.
On the other hand, people have to trust the synthetic data is good enough to use Practically.
So you have to both convince management and convince engineers. Arguably management is easier to convince, but.. best of luck on the endeavor!
That’s not even discussing the technical challenges - I’ve implemented this all technically and have had it deployed to production systems. Building a robust system that is secure and produces valid synthetic data is a challenge.
We'll be releasing some of the packages to do the analysis and transformations as time goes on, so stay tuned for those so you can take them for a test drive yourself.
Thanks!
The problems with a 'Github for data' are the 7 'V's Volume: too much data to have usable diffs and merges Veracity: How do you know which branch of data to commit? Velocity: The data coming in is a stream - batch processing does not cut it
Most companies end up creating a federation, not a true Data Mart.
It feels like we can tease those two things apart:
1. Is a github-style website/service of forkable data sets useful?
2. Are anonymized, synthetic versions of those data sets, created via ML, useful?
Feels like the answer to both is "yes"?
(Also makes me wonder if there's a "rebase" equivalent for data in this sort of world...)
Depends on the specifics, but it can be.
I've been working on and off on getting a GitHub style data thing going (https://dbhub.io).
It's still a work-in-progress, and I really need to get the data visualisation piece working, which is a pretty key feature and lousy to not have. ;)
While I do see your point about trusting an external company which is specialized in the problem I’m trying to solve more than my own developers, I still have to transfer my highly sensitive data to them for which I have to trust them even more.
FEDRAMP it. Now run that as a service inside a secure cloud environment. You need enough runway for the FEDRAMP / engineering / sales process plus a contract win and then I'd imagine the income gets pretty steady.
Commercially? Unsure of the use case. I'd imagine as those sharing data are typically in competition. Not so in the government / intel community / finance space and I'd imagine you have to write a metric ton of policy and sign a bunch of MOUs to do this kind of stuff properly. People in government do care a great deal about these policies, believe it or not.
This is also a huge problem to solve in the "Know Your Customer" / Anti-Money Laundering space for financial institutions, where sharing data between companies or government and companies is often prohibited and/or really difficult. See the recent FCA TechSprint for more on this: https://www.fca.org.uk/events/techsprints/aml-financial-crim...
Lots of talk of "Homomorphic Encrpytion" and "Encrypted Cloud Runtimes" as options but if you don't really need to share all of the data to get to an outcome (but rather synthetic data - though synthetic identity seems to be the hard bit here...) that could be interesting!
[1]: https://github.com/geraldb/talks/blob/master/git_for_data.md
https://medium.com/gretel-ai/using-generative-differentially...
People in the Privacy-preserving industry try to find the silver bullet in one technology, but the real solution is a combination of different technologies. Trusted delegation of computation + privacy-preserving techniques together solve this issue, but separately provide marginal value.
But maybe I'm wrong?
I just looked at their website, and they don't mention anything about NSA, Amazon, or Google on the landing page, so I think it's just techcrunch adding it in as clickbait, even though the founders aren't going out of their way to advertise it.
NSA engineers on average would be scary good.
I needed a Resitivity-Temperature dataset for a Tungsten alloy and I ended up having to manually type up a series out of the book, not fun!
If not, is this a common name in Hungary? Small world.
This is the correct link
Git for data to us means a SQL database with Git semantics, backed by a content addressed graph of rows. That's what we built.
Plus, we own http://www.gitfordata.com, so we win.
Consider a SAAS with 25,000 active customers and tons of structured (database) data.
You have a bunch of people that need to work on the dev system and the closer dev looks to prod the better you are.
- Contractors in another country
- A team working on basic compliance with GDPR and CCPA
- Sysadmin team trying to manage backups/restores
When the contractors pull a version of the DB it needs to not have any customer data (emails, addresses, etc.) so there's a process that wipes all those out and fills them in with fake data.
When the GDPR team gets a data deletion request ("Please delete all my data my email is X@y.com") on Monday and the Sysadmin team restores from a backup from Sunday what happens?
Right now both of these actions are one-off things done with a mish-mash of scripts, organizational knowledge, and half-remembered processes.
So wouldn't this be better with a service that could talk to your DB and you could fork out versions that "knew" the current DB structure, that you could mark as purged of sensitive data, that you could apply (and re-apply) transforms to for structure to data addition/removal.
Naive take?
git lfsHere's an example (or shameless plug): I use GitHub to share research data: https://github.com/btrettel/pipe-jet-breakup-data
There's code in that repository too. The code merges a variety of different data sources and performs some analyses. Nothing particularly fancy, and the code is probably not much better than average as far as academic code goes (which is not good), but I'm slowly adding tests and improving the code otherwise.
Anyone taking bets on how long it's going to be before these idiots end up leaking the SSN of every US citizen because their categorizer failed?
See for example the videos on https://hazy.com/product
Disclosure: Hazy cofounder.
Anonymised data or redacted data are transformations of a data set that _hopes_ not to leak too much PII / sensitive data. People don’t use ML to anonymise but they do use ML to classify as a first step before splatting or generalising.
In that case, its absolutely right that the ML classifier not being 100% results in PII leaking.
This is a key reason why anonymisation and redaction are widely seen as problematic and are being replaced by synthetic data and, maybe in future, homomorphic encryption.
There are nuances — like static vs dynamic distributions and whether the downstream model is actually just aggregating anyway.
I’m my username at hazy.com if you’d like to connect.