Stijn Muylle Profile
Stijn Muylle

@ddccffvv

Followers
100
Following
349
Media
33
Statuses
1K

Will tweet once in a while, about whatever interests me. Likely subjects: tech, indiehackers, infosec, climate change

Joined April 2009
Don't wanna be here? Send us removal request.
@ddccffvv
Stijn Muylle
5 years
I have some extra time in the coming months and I'd like to use it to start a small research project: I want to make a catalog of the security / privacy clauses that large enterprises often require in their contracts.
Tweet media one
2
0
0
@ddccffvv
Stijn Muylle
7 months
RT @DecryptedTech: @ImposeCost @bettersafetynet Let's not forget the industry's short attention span and lack of long-term memory.
0
2
0
@ddccffvv
Stijn Muylle
8 months
Bug Bounty submission status: pending. 😓😓.
0
0
0
@ddccffvv
Stijn Muylle
2 years
RT @AccidentalCISO: If you don’t like working with people, managing relationships, brokering deals, and finding ways to build influence out….
0
14
0
@ddccffvv
Stijn Muylle
2 years
RT @HackingLZ: Infosec has a short memory forgetting all the marketing around ML stuff that was pushed years ago. It was the magic fix to s….
0
12
0
@ddccffvv
Stijn Muylle
2 years
RT @patio11: You’d be surprised of how much of management, consulting, teaching, senior ICing, etc is:. ā€œI want to X.ā€.ā€œHave you written do….
0
171
0
@ddccffvv
Stijn Muylle
2 years
RT @LuckyMcGee: Found the forest where Home Depot gets their lumber.
Tweet media one
0
932
0
@ddccffvv
Stijn Muylle
2 years
RT @_workchronicles: Learn to say No
Tweet media one
0
464
0
@ddccffvv
Stijn Muylle
2 years
here's a hot take: I think false positives (in infosec) are overrated as an issue. Instead, what's more important is the time spent to chase down and confirm no-issue. If that was instantaneous, we wouldn't care much about potential false positives. *ducks*.
0
0
0
@ddccffvv
Stijn Muylle
2 years
Am I looking at this wrong? (Asking for a friend šŸ˜‡).
0
0
1
@ddccffvv
Stijn Muylle
2 years
But it seems a bit depressing from the founder point of view: bigco seems to have an insurmountable advantage when the idea is to integrate with (or assimilate) other tooling. Whereas small teams can often create an advantage where they are "the best" in a niche thing.
1
0
1
@ddccffvv
Stijn Muylle
2 years
Also notice the nugget on security tooling consolidation for the next few years. This seems to be the consensus around the industry (and understandably: defence has been drowning in tools and alerts for too long).
1
0
1
@ddccffvv
Stijn Muylle
2 years
I always admire it when someone puts his thoughts into words, it takes much more thought and courage than a throwaway tweet storm. Here is @txs with his view on the next years in cybersecurity: Worth a read!.
1
0
1
@ddccffvv
Stijn Muylle
2 years
Raise your hand if you've seen this situation before šŸ™‹ā€ā™‚ļø. from @DanielMiessler's blog post (. Read the whole thing, it's worth it. One can only hope he's right about the SEC intention and industry maturing.
Tweet media one
0
0
0
@ddccffvv
Stijn Muylle
2 years
What is the way to have some kind of approval flow to request resources? Ie: dev requests a s3 bucket and manager approves. Something low friction?.
0
0
0
@ddccffvv
Stijn Muylle
2 years
RT @paularambles: if you’re not in tech then all you need to know about the past weekend is that your tech friends went through like three….
0
1K
0
@ddccffvv
Stijn Muylle
2 years
RT @DanielMiessler: The first rule for implementing something with machine learning or blockchain…is to figure out if you can implement it….
0
58
0
@ddccffvv
Stijn Muylle
2 years
RT @planetlevel: @ddccffvv Over 62% of open source libraries are completely inactive - never even load into memory. Of code that does run,….
0
1
0
@ddccffvv
Stijn Muylle
2 years
However, if you tell me I can only pick one scenario, I'm going with B (shift left be damned!). I'm fixing actual issues late, instead of hoping I've fixed everything early. Not even hesitating.
1
0
1
@ddccffvv
Stijn Muylle
2 years
@planetlevel Scenario B is then an opportunity to get to the root cause. The best goal here might not be a "quick time to fix", but answering the question: "why did we not catch this issue earlier?".
3
0
0