<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: alexsmolen</title><link>https://news.ycombinator.com/user?id=alexsmolen</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 25 Apr 2026 09:10:49 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=alexsmolen" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: TrailTool – open-source CLI for querying CloudTrail data with AI agents]]></title><description><![CDATA[
<p>I've been working on AWS security for years and querying CloudTrail has always been a huge pain - getting data about like "what did this role actually use in the last 30 days?" means either writing custom queries and result parsing code or getting vague data from built-in tools like Access Analyzer.<p>TrailTool's core idea is to pre-aggregate CloudTrail events at ingest time into entity relationships — People, Sessions, Roles, Services, Resources — so queries are DynamoDB reads rather than log scans. The CLI talks directly to your DynamoDB tables using standard AWS credentials, no API layer needed.<p>The four workflows in the post (ClickOps detection, least-privilege policy generation, AccessDenied remediation, break-glass validation) all came from things I was actually doing manually. The session transcripts are real Claude Code runs using the tool.<p>Wondering if this feels useful to folks, or if there are other CloudTrail questions that could be pre-computed this way to accomplish common tasks.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47507510">https://news.ycombinator.com/item?id=47507510</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 24 Mar 2026 18:59:40 +0000</pubDate><link>https://github.com/engseclabs/trailtool</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=47507510</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47507510</guid></item><item><title><![CDATA[New comment by alexsmolen in "Ask HN: What are you working on? (February 2026)"]]></title><description><![CDATA[
<p>I'm working on TrailTool, which aggregates CloudTrail for analysis in both UI and AI contexts. I've always found it tough to tie together CloudTrail logs into meaningful narratives useful not only for security investigations but also "role engineering" (i.e. reducing privileges on human-operated IAM roles). The idea is to make this info available via MCP for agent workflows as well, so you can get high quality, low latency, manageable context size CloudTrail data.<p>If you want to kick the tires, you an deploy a CloudFormation stack to a Sandbox AWS account - see <a href="https://trailtool.io/install.html" rel="nofollow">https://trailtool.io/install.html</a></p>
]]></description><pubDate>Mon, 09 Feb 2026 22:49:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=46952695</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=46952695</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46952695</guid></item><item><title><![CDATA[New comment by alexsmolen in "Company as Code"]]></title><description><![CDATA[
<p>In my research I haven’t come across the prior art you suggest exists. The trust centers you linked aren’t fungible with what I’m building with GraphGRC. The idea is to make all your security docs just a GitHub repo with structured markdown that permits useful automation (e.g. generating linked internal site, validating all docs have been “reviewed” annually by checking metadata, change control via PR, etc.)<p>There are plenty of GRC products out there and are popular for good reasons, but I don’t think any of them are Git/Markdown/developer-first.</p>
]]></description><pubDate>Thu, 05 Feb 2026 16:45:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=46901591</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=46901591</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46901591</guid></item><item><title><![CDATA[New comment by alexsmolen in "Company as Code"]]></title><description><![CDATA[
<p>I love this idea despite the real world operational challenges - most people with governance responsibilities in organizations don't want to code, and code is often too precise to model messy social/organizational context without constant tweaking, tending, and exception management.<p>I'm an advocate for bringing software culture to GRC, or as it's sometimes called “GRC Engineering”. While there are plenty of products to automate evidence generation for auditors, the underlying policies and documents that they prescribe are usually still old-school Word/PDF-style boilerplate junk.<p>I'm working on an open source project for security policies/processes/standards that map back to underlying frameworks (e.g. SOC 2, GDPR, ISO 27001, etc.) Docs are Markdown with YAML frontmatter metadata, interlinks generated automatically, site is published via GitHub actions.<p>The code is at <a href="https://github.com/engseclabs/graphgrc" rel="nofollow">https://github.com/engseclabs/graphgrc</a>, and you can see an example published site here <a href="https://graphgrc.engseclabs.com" rel="nofollow">https://graphgrc.engseclabs.com</a>.<p>Would love to know if others find it useful or have built similar systems.</p>
]]></description><pubDate>Thu, 05 Feb 2026 16:07:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=46901179</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=46901179</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46901179</guid></item><item><title><![CDATA[What Should I Work on Next? A Framework for High-Impact Security Work]]></title><description><![CDATA[
<p>Article URL: <a href="https://engseclabs.com/blog/what-should-i-work-on-next/">https://engseclabs.com/blog/what-should-i-work-on-next/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45904358">https://news.ycombinator.com/item?id=45904358</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 12 Nov 2025 18:56:51 +0000</pubDate><link>https://engseclabs.com/blog/what-should-i-work-on-next/</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=45904358</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45904358</guid></item><item><title><![CDATA[Backyard Apt: A Raccoon Story]]></title><description><![CDATA[
<p>Article URL: <a href="https://engseclabs.com/blog/raccoon-diaries/">https://engseclabs.com/blog/raccoon-diaries/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45904306">https://news.ycombinator.com/item?id=45904306</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 12 Nov 2025 18:54:46 +0000</pubDate><link>https://engseclabs.com/blog/raccoon-diaries/</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=45904306</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45904306</guid></item><item><title><![CDATA[Refocusing Vendor Security on Risk Reduction]]></title><description><![CDATA[
<p>Article URL: <a href="https://engseclabs.com/blog/refocusing-vendor-security-on-risk-reduction/">https://engseclabs.com/blog/refocusing-vendor-security-on-risk-reduction/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45440616">https://news.ycombinator.com/item?id=45440616</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 01 Oct 2025 17:39:53 +0000</pubDate><link>https://engseclabs.com/blog/refocusing-vendor-security-on-risk-reduction/</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=45440616</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45440616</guid></item><item><title><![CDATA[Small language model for secrets detection]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.wiz.io/blog/small-language-model-for-secrets-detection-in-code">https://www.wiz.io/blog/small-language-model-for-secrets-detection-in-code</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44351556">https://news.ycombinator.com/item?id=44351556</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 23 Jun 2025 00:53:33 +0000</pubDate><link>https://www.wiz.io/blog/small-language-model-for-secrets-detection-in-code</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=44351556</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44351556</guid></item><item><title><![CDATA[Securing GitHub Organizations]]></title><description><![CDATA[
<p>Article URL: <a href="https://alsmola.medium.com/securing-github-organizations-9c33c850638">https://alsmola.medium.com/securing-github-organizations-9c33c850638</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=29943669">https://news.ycombinator.com/item?id=29943669</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 15 Jan 2022 04:51:55 +0000</pubDate><link>https://alsmola.medium.com/securing-github-organizations-9c33c850638</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=29943669</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29943669</guid></item><item><title><![CDATA[New comment by alexsmolen in "Building Webhooks into Your Application: Guidelines and Best Practices (2020)"]]></title><description><![CDATA[
<p>This is a pretty good article about preventing SSRF including DNS rebinding-based attacks in Go <a href="https://www.agwa.name/blog/post/preventing_server_side_request_forgery_in_golang" rel="nofollow">https://www.agwa.name/blog/post/preventing_server_side_reque...</a></p>
]]></description><pubDate>Tue, 09 Mar 2021 21:53:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=26404850</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=26404850</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=26404850</guid></item><item><title><![CDATA[New comment by alexsmolen in "Building Webhooks into Your Application: Guidelines and Best Practices (2020)"]]></title><description><![CDATA[
<p>Kind of wild that there's no mention of SSRF. A quick search shows it's a pretty frequent security issue in Webhooks: <a href="https://www.google.com/search?q=ssrf+webhook" rel="nofollow">https://www.google.com/search?q=ssrf+webhook</a></p>
]]></description><pubDate>Tue, 09 Mar 2021 19:45:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=26403129</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=26403129</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=26403129</guid></item><item><title><![CDATA[Use AWS Glue to Make CloudTrail Parquet Partitions]]></title><description><![CDATA[
<p>Article URL: <a href="https://medium.com/@alsmola/use-aws-glue-to-make-cloudtrail-parquet-partitions-c903470dc3e5">https://medium.com/@alsmola/use-aws-glue-to-make-cloudtrail-parquet-partitions-c903470dc3e5</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=23762238">https://news.ycombinator.com/item?id=23762238</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 07 Jul 2020 18:11:14 +0000</pubDate><link>https://medium.com/@alsmola/use-aws-glue-to-make-cloudtrail-parquet-partitions-c903470dc3e5</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=23762238</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=23762238</guid></item><item><title><![CDATA[New comment by alexsmolen in "Ask HN: Any “Git diff”-like service but for when terms of conditions changes?"]]></title><description><![CDATA[
<p>This is what <a href="https://tosback.org/" rel="nofollow">https://tosback.org/</a> does, I believe.</p>
]]></description><pubDate>Mon, 18 Nov 2019 15:38:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=21565109</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=21565109</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=21565109</guid></item><item><title><![CDATA[Wag: A Go Web API Generator]]></title><description><![CDATA[
<p>Article URL: <a href="https://medium.com/always-a-student/wag-a-go-web-api-generator-7eeb901de60b">https://medium.com/always-a-student/wag-a-go-web-api-generator-7eeb901de60b</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=16700486">https://news.ycombinator.com/item?id=16700486</a></p>
<p>Points: 6</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 28 Mar 2018 18:39:03 +0000</pubDate><link>https://medium.com/always-a-student/wag-a-go-web-api-generator-7eeb901de60b</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=16700486</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=16700486</guid></item><item><title><![CDATA[Implementing the sudo access pattern for AWS IAM Users]]></title><description><![CDATA[
<p>Article URL: <a href="https://medium.com/@alsmola/implementing-the-sudo-access-pattern-for-aws-iam-users-268307e28e19">https://medium.com/@alsmola/implementing-the-sudo-access-pattern-for-aws-iam-users-268307e28e19</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=16312958">https://news.ycombinator.com/item?id=16312958</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 05 Feb 2018 22:48:12 +0000</pubDate><link>https://medium.com/@alsmola/implementing-the-sudo-access-pattern-for-aws-iam-users-268307e28e19</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=16312958</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=16312958</guid></item><item><title><![CDATA[Creating IAM resources and policies simply with terrafam]]></title><description><![CDATA[
<p>Article URL: <a href="https://medium.com/@alsmola/iam-simply-with-terrafam-c436241c4054">https://medium.com/@alsmola/iam-simply-with-terrafam-c436241c4054</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=14806713">https://news.ycombinator.com/item?id=14806713</a></p>
<p>Points: 6</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 19 Jul 2017 18:37:33 +0000</pubDate><link>https://medium.com/@alsmola/iam-simply-with-terrafam-c436241c4054</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=14806713</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=14806713</guid></item><item><title><![CDATA[New comment by alexsmolen in "Early Warning Detectors Using AWS Access Keys as Honeytokens"]]></title><description><![CDATA[
<p>Yeah, I think it’s tricky to figure out how to place it somewhere that attackers would look but AWS tooling wouldn’t, by default, since otherwise they may be used in legitimate operation.</p>
]]></description><pubDate>Wed, 30 Nov 2016 22:50:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=13075438</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=13075438</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=13075438</guid></item><item><title><![CDATA[New comment by alexsmolen in "Secret Management with Vault"]]></title><description><![CDATA[
<p>I recently helped build a secret store system for our infrastructure, and we decided to not use Vault.<p>A big reason was that Vault’s AWS authentication backend is not based on AWS infrastructure like IAM/KMS, but uses a somewhat backhanded method (<a href="https://www.vaultproject.io/docs/auth/aws-ec2.html" rel="nofollow">https://www.vaultproject.io/docs/auth/aws-ec2.html</a>) to establish verify an EC2 instance. We use ECS, and it doesn't play well with it - see <a href="https://github.com/hashicorp/vault/issues/1298" rel="nofollow">https://github.com/hashicorp/vault/issues/1298</a><p>Instead, we would have had to fall back to the App ID method, which requires separate configuration, and is “Trust On First Use” so doesn’t offer as strong of security guarantees in my opinion.<p>Also, the only Hashicorp supported-backends are file (non-HA) and Consul.<p>If you're all-AWS, I'd recommend checking out Confidant/Knox (run as a separate service) or Credstash/Biscuit (run directly against AWS infra).</p>
]]></description><pubDate>Fri, 28 Oct 2016 22:43:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=12821388</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=12821388</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=12821388</guid></item><item><title><![CDATA[New comment by alexsmolen in "There are limits to 2FA"]]></title><description><![CDATA[
<p>The problem is that SMS provides better recovery rates than TOTP/HOTP + backup codes, because people can go to their carrier and get a new device at the same number.<p>It's important to remember that availability is an important aspect of security. If you protect a user primarily concerned with mass-account takeover attacks from a low-probability threat (people intercepting their SMS channel) but introduce a high-probability threat (dropping their phone in the toilet and being locked out of their account forever) you may not have made a good security tradeoff.</p>
]]></description><pubDate>Mon, 01 Aug 2016 01:35:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=12199754</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=12199754</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=12199754</guid></item><item><title><![CDATA[18F caused a data breach using Slack]]></title><description><![CDATA[
<p>Article URL: <a href="http://www.nextgov.com/cio-briefing/2016/05/watchdog-18f-caused-data-breach-using-slack/128288/?oref=nextgov_breaking_alert">http://www.nextgov.com/cio-briefing/2016/05/watchdog-18f-caused-data-breach-using-slack/128288/?oref=nextgov_breaking_alert</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=11692038">https://news.ycombinator.com/item?id=11692038</a></p>
<p>Points: 18</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 13 May 2016 18:00:58 +0000</pubDate><link>http://www.nextgov.com/cio-briefing/2016/05/watchdog-18f-caused-data-breach-using-slack/128288/?oref=nextgov_breaking_alert</link><dc:creator>alexsmolen</dc:creator><comments>https://news.ycombinator.com/item?id=11692038</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=11692038</guid></item></channel></rss>