1,023 karma · joined March 7, 2015
For comparison, I think Mac OS in 2008 was also at a bit of a golden age:
- You had native file support for .iso, .zip without needing to install crapware like Winzip.
- You even could preview *.psd files out the box.
- You had first-party apps like Image Capture to scan documents without needing to install extra software.
- There was an amazing third-party app ecosystem with things like Yojimbo, OnyX, Little Snitch, Quicksilver, Handbrake, Coda, Adium.
This was around the time of the "I'm a Mac" campaign when Apple was _hungry_ to win business away from Windows. All of these small, polished advantages made me fall in love with the experience.
OSX today is still good but there definitely isn't that same level of "underdog hunger" showing up in the products as of late.
Anyway I'm just trying to say companies being hungry for business shows up in its products and that's better for consumers.
[ ] Added unit tests
[ ] Included a screenshot of the code working (this helps reviews go faster)
I learn so much more when a professor has a whiteboard and writes out an equation is derived one step at a time.
I see both sides of this. When I was a teenager, I went to a pretty bad middle school where there were fights everyday, and I wasn’t learning anything from the easy homework. On the upside, I had tons of free time to teach myself how to make websites and get into all kinds of trouble botting my favorite online games.
My learning always hit a wall though because I wasn’t able to learn programming on my own. I eventually asked my parents to send me to a school that had a lot more structure (and a lot more homework), and then I properly learned math and logic and programming from first principles. The upside: I could code. The downside: there was no free time to apply this knowledge to anything fun
Or, I have a docker container image that is built from multiple base images owned by different teams in my organization. Who is responsible for fixing security vulnerabilities introduced by each layer?
We really could model these as tables but getting into all those joins makes things so cumbersome. Plus visualizing these things in a graph map is very compelling for presentation and persuading stakeholders to make security decisions.
Automated review tools like this are especially important for an open source project because you have to maintain a quality bar to keep yourself sane but if you're too picky then no one from the community will want to contribute. AI tools are like linters and have no feelings, so they will give the feedback that you as a reviewer may have been hesitant to give, and that's awesome.
Oh, and on the product itself, I think it's super cool that it comes up with rules on its own to check for based on conventions and patterns that you've enforced over time. E.g. we use it to make sure that all function calls that pull from an upstream API are decorated with our standard error handler.
For a higher level view and contextualization, can you share more on what you mean? This would help give us a better idea on what to build.
> I was considering a demo, but the two options (chat and quick chat) were a bit unclear to me what they would archive / how they are structured.
Ah, you're referring to our cal link (https://cal.com/team/subimage)? It's basically up to you -- we can show you something in 15 minutes or 30 minutes based on your availability and based on what you're interested in -- would love to hear feedback in call!
> what I'm asking is whether you envision your future as one of ("eh, it's good enough", "we're integrating more libraries that attempt to formalize IAM", or "we'll roll our own policy engine in python, how hard could it be")
It's a combination of 2 and 3. Today we use the policyuniverse library for things like s3 bucket-policies, and we have that self-rolled policy engine described in that blog post I shared. I should've mentioned earlier that this is the first time I've seen IAMSpy, thanks for sharing.
I think we're currently pretty good at permissions evaluation since that feature gives lots of value as it is, but there is a lot more to do. Continuing to improve this and being able to connect that with other data is a priority since it's one of our main value propositions.
> there is a massive opportunity for expectations being out of alignment unless you have a plan to get from where you are to Industrial Grade Introspection.
Industrial Grade Introspection is absolutely the plan. I'll also add that we're especially interested in highlighting cases that involve permissions that go between providers - like Okta->AWS, Opal->AWS, etc - and we intend to be very competitive here.
> Found Splunk creds in a log? Awesome, start using them. Syslog in an S3 bucket... boom. You are now hitting the stuff that every other ASM/visualization tool has missed.
This is my dream :). This past weekend I was playing around with something where if I clicked on a SecretsManagerSecret node then it'd give me the CLI commands to assume the roles and then retrieve the secret. It'd be neat to take it a step further and be able to click here and get a shell -- I don't think we're _that_ far off from that (but for now to be very clear we're focusing on read-only actions only since a security tool with permissions to do scary things in your environment kinda defeats the purpose).
We 100% do this, see https://eng.lyft.com/iam-whatever-you-say-iam-febce59d1e3b.
We evaluate the policies for the IAM principal against the resources to determine what actions they can perform on each resource. This is configurable too; here's the set of the default permission relationships shipped in OSS: https://github.com/cartography-cncf/cartography/blob/master/...
It doesn't cover conditions since those can be wacky complicated, and it doesn't cover resource policies (yet!) but in my experience this is still a very good heuristic that is already more accurate than AWS IAM Analyzer when I played with it.
The next step we're working on is to take this access map and correlate it with event data to see which permissions are used/unused so that we can prune them for ensuring least privilege. More to come here.
Edit: adding on for the part of your question about what features are paid or OSS, our paid offering is fully hosted and includes things like automatic suggested fixes, a natural language interface, customization with our dynamic schemas, and other bells and whistles. I'm not a fan of doing things like premium modules because I don't want to ever get in the position where I'm declining a pull request in open source because it covers a premium feature; that doesn't feel right.
We recommend changes, though we don't generate Terraform just yet. Great feedback on the specific fixes for this case, thanks.