Sym

Embrace your best security asset: your team

Trusted by @ASICSamerica, @Fundapps, @Bryter_IO, @_jellyfish_co

[Sym @symops]

We are officially live on @ProductHunt 🔥

Check us out and leave your feedback 👇

https://t.co/E2qgXKJqX6

[Sym @symops]

💥 Major announcement: we've officially released our dynamic authorization platform!

What's new?
- Web app
- Context-based access controls
-Partnerships & integrations

Read more on what we've launched here: https://t.co/aqCbptUr2C

[Sym @symops]

🚨 New blog post alert! Learn why making mistakes – and responding to them well – is such an important part of building a positive engineering culture: https://t.co/lZGWQGY61r

[Sym @symops]

📈 2022 showed a massive 81% increase in phishing hacks... has modern tooling contributed to this increase by making phishing schemes easier?

Read @mathewpregasen's take here ➡ https://t.co/BqzcuFz4Ag

[Sym @symops]

📖 Check out our JIT access guide for info on:

- The principle of least privilege
- Least privilege in the cloud and AWS
- Replacing risky access with automation

Full guide available here: https://t.co/18epnGYV7u

[Sym @symops]

There are 3 stages of evolution when it comes to access management:

1. Controlled Anarchy
2. Stumbling Maturity
3. Sedimented Bureaucracy

So... what should you do to implement security without creating bottlenecks?

Read the full post here: https://t.co/iplQTDNlOU

[Sym @symops]

Building a best-fit solution for audited, temporary access on your own sounds great until you think about:

1. Cost
2. Where eng time would actually be spent

So what do you do? Read our take here: https://t.co/ADlX1EnwGT

[Sym @symops]

With Sym, Orum is able to implement JIT access ➡️ "Not having engineers that have stagnant or over-privileged AWS policies assigned within their accounts or different environments 24x7 makes me sleep a little bit better at night."

Full case study here: https://t.co/XFcmNV5hSO

[Sym @symops]

🚨 New post alert! How many security issues could we avoid if we knew the answer to “has this person ever done this thing before?” The answer: a lot

Check out how Sym's newest feature, Historical Context, makes it easy to answer that question: https://t.co/N0cRWlB0tU

[Sym @symops]

Did you know that Sym has a @HashiCorp HCP Boundary integration? Check it out here:

[DevOpsDays Chicago @devopsdaysChi]

Big thank you to our transcription sponsor @symops for supporting DevOpsDays Chicago. #DevOpsDaysChi

[Sym @symops]

@HashiCorp For a full list of our recent updates + to stay tuned for what's next 👀 check out our changelog here: https://t.co/0aNynSL3fD

[Sym @symops]

Have you been keeping up with our changelog? If not... you should 😜 check out our surge of new features from the last few weeks 👇

[Sym @symops]

8/9 Sym adds support for @Hashicorp Boundary groups: now you can use Sym + Boundary to...

- Filter your target lists based on user context
- Support a programmable request-approve cycle that fits your security and compliance needs

[AWS Security Digest @AwsSecDigest]

🥇 This week's most popular link comes from @abuggia @symops

https://t.co/ezE2w9TWZK

[Sym @symops]

Sym’s just-in-time access solution is officially live in AWS Marketplace!

Now, you can use AWS Marketplace’s 1-click deployment to get up and running on Sym quickly, with payments processed directly via AWS.

Check it out here: https://t.co/INXeGSvDMT

[Sym @symops]

With Sym, you just configure default backup destinations for your request, timeouts, and an (optional) expiration.

No more hanging requests, no more access blockage.

📣 Release note: https://t.co/UlvhBQUByn
🗒️ Docs: https://t.co/8QXW3i8NIE

Like I said, short thread. (2/2) 👋

[Sym @symops]

🚨 New feature drop 🚨

Introducing: backup approver chains --

Let's say the person whose approval you need is on PTO 🌴. Or maybe you accidentally deleted the Slack channel where all your requests need to go 🙀!

What then, hmm? (Short) thread below 🧵👇 (1/n)