Solanasis LinkedIn Company Page Cheat Sheet

Created: April 1, 2026 Voice: “We/our” with same sharp casual energy as personal page Primary CTA: Email list signup (Brevo) Cadence: 2x/week (Tuesday + Friday)


Page Strategy at a Glance

Personal Page (Dmitri)Company Page (Solanasis)
Voice”I/my”, personal opinion”We/our”, same energy
ContentThought leadership, teaching, toolsNews roundups, service spotlights, alerts
CTANone (helpful content stands alone)Email signup link
Cadence2-3x/week2x/week
GoalBuild authority + personal brandBuild email list + establish credibility

Weekly Posting Calendar

Tuesday: Security News Roundup

  • 3-5 security/tech news items from the past week + Solanasis take
  • Tone: “Here’s what happened. Here’s why it matters.”
  • CTA: Email signup (weekly intel angle)

Friday: Service Spotlight OR Practical Alert (alternate weekly)

  • Week A (Spotlight): Deep look at one Solanasis service with client context
  • Week B (Alert): Time-sensitive security alert, patch urgency, or compliance deadline
  • CTA: Email signup or soft link to service page

Personal Page Complement

  • Dmitri posts on different days to avoid competing
  • When Dmitri drops deep opinion, company page can amplify with “Our take” the following Tuesday
  • Company page stays newsy/tactical; personal page stays strategic/philosophical

Content Pillars

1. Security News & Threat Intelligence (Tuesday)

Frequency: Weekly Topics: New CVEs, ransomware campaigns, compliance shifts, breach analysis, vendor incidents Hashtags: CyberSecurity ThreatIntel SMBSecurity SecurityNews

2. Service Spotlights (Alternating Friday)

Frequency: Biweekly Topics: Assessment walkthroughs, DR verification stories, integration wins, AI implementation Hashtags: CyberSecurity GovernanceMatters SecurityLeadership RiskManagement

3. Practical Security Alerts (Alternating Friday)

Frequency: Biweekly Topics: Urgent patches, compliance deadlines, time-sensitive vulnerabilities Hashtags: CyberSecurity SecurityAlert Compliance ActionableIntel

4. Industry Commentary (Occasional)

Frequency: 1-2x/month when the moment calls for it Topics: Zero Trust philosophy, compliance vs. security, contrarian takes Hashtags: CyberSecurity SecurityThinking SMBInsights

5. Team & Culture (Occasional)

Frequency: Monthly Topics: Hires, certifications, speaking engagements, milestones Hashtags: CyberSecurity SolanasisTeam CareersInCyber


Email Signup CTA Library (Pick One Per Post)

  1. We send a weekly email with the stuff that actually matters for small orgs. Sign up here: [link]
  2. Want these insights in your inbox every week? [link]
  3. Tired of security theater? We send the real stuff weekly: [link]
  4. Get this roundup delivered before your Friday coffee: [link]
  5. Skip the noise. We curate the signal and send it weekly: [link]
  6. Your team should see this. Add your email and we’ll make sure they do: [link]
  7. Want unfiltered takes on security news? We’ve got you: [link]
  8. Add your email; we send practical security context every week: [link]
  9. Getting blindsided by security stories? Stop: [link]
  10. These weekly briefings are exactly what ops teams need: [link]
  11. Your inbox needs this. Let’s fix that: [link]
  12. Know before your vendors know you know: [link]
  13. Not reading security news? Your inbox is about to change: [link]
  14. We send a weekly digest on threats that don’t make mainstream news but absolutely impact small teams: [link]
  15. We send a weekly email on what actually moves the needle for small org security: [link]

Reusable Weekly Roundup Template

[Hook: 1 line with a striking stat or observation]

[Context: 2-3 lines on why this matters for small orgs]

Key takeaways:
• [Point 1]
• [Point 2]
• [Point 3]

Here's the thing: [insight that connects back to SMB reality]

[CTA variant from library above]

Tone Checklist:

  • Casual opener (no corporate speak)
  • Teaching as we go (explain the why)
  • SMB-focused (not enterprise theater)
  • No engagement bait questions
  • One soft CTA at the end
  • 8-12 lines total (scannable)
  • No banned words

Cross-Promotion Templates (Company Amplifies Personal)

Template 1: Extended Take

Our CEO @Dmitri Sunshine shared his take on [topic] this week. Here’s why it matters for security leaders managing SMB budgets: [1-2 sentence practical extension]. Worth the read if you’re thinking about [topic] differently.

Template 2: News Hook + His Expertise

[News headline]. @Dmitri Sunshine wrote about this exact pattern on his personal page. If you’re managing security at an SMB, this is the moment to read both and ask yourself the hard questions.

Template 3: Evidence Layer

@Dmitri Sunshine dropped a take on [topic] and we’ve got layers to add. He’s right that [agree on main point]. Here’s what we see in audit rooms that changes the conversation: [evidence from engagements].


READY-TO-POST CONTENT


NEWS ROUNDUPS


Iran Cyber Escalation: What It Means for Small Orgs

Style A: Explainer

Iran’s cranking up cyber operations against anything cloud-based. Akamai’s seeing a 245% spike in credential theft, reconnaissance, and DDoS setup targeting financial firms.

Here’s what’s happening: proxy groups tied to Iran (Handala Hack, DieNet) are actively scanning AWS, Azure, and Oracle Cloud infrastructure. They’re going after banks, fintech payment gateways, energy traders. One group even claimed a destructive malware hit on a US medical device company.

Which is why this matters for small orgs: • Your cloud infrastructure is on the same platforms they’re targeting • If you’re in financial services, payments, healthcare, or energy: you’re in their crosshairs • 5 days. That’s median time from intrusion to ransomware execution • Your credentials are the entry point. Weak auth is already compromised

Here’s the thing: geopolitical cyber escalation doesn’t skip small organizations. It just exploits them harder because they run on hope and luck.

We send a weekly email on threats that actually matter for small teams. Sign up here: [link]

CyberSecurity ThreatIntel SMBSecurity Iran SecurityNews


Style B: Sharp Take

Geopolitical tensions just became your cybersecurity problem. Iran’s cyber groups are actively hunting cloud infrastructure, and they’re not checking company size before they attack.

The numbers: 245% increase in credential harvesting attempts. Targets are financial services, payment platforms, healthcare, energy. Their playbook is predictable: get credentials, map the network, stage ransomware, execute.

What SMBs get wrong about this: • You think “that’s a big-org problem” (it’s not) • You assume your cloud provider handles security (they don’t handle yours) • You’re still using password reuse and weak MFA (if any) • 5 days until execution means you’re already too late if detection takes longer

Let’s be frank: geopolitical cyber threats hit small orgs first because they’re the gap in security maturity. No SOC (Security Operations Center), no threat intel, no incident response plan.

We send a weekly digest on threats that don’t make mainstream news but absolutely impact small teams. Sign up: [link]

CyberSecurity ThreatIntel SMBSecurity FinancialServices SecurityNews


Style C: Stat-Led

245% increase in credential harvesting attempts. Target: financial services. Actors: Iranian proxy groups with destructive malware capabilities.

Here’s what the Canadian Centre for Cyber Security and US banking regulators are warning about right now:

• Handala Hack and DieNet are actively scanning AWS, Azure, Oracle Cloud • Cloud infrastructure in financial services and healthcare is priority target • Median time to ransomware execution: 5 days from first intrusion • 88% of SMB breaches last year involved ransomware

Which is why: if your small org runs on cloud infrastructure and doesn’t have real-time threat detection, you’re running on borrowed time.

We send a weekly email about threats that matter for organizations without a dedicated security team. Sign up here: [link]

CyberSecurity ThreatIntel SMBSecurity SecurityAlert


SMBs Are Still the #1 Target (2026 Numbers)

Style A: Reality Check

SMBs are getting hit harder than anyone else, and the 2026 numbers prove it.

43% of all cyberattacks target small businesses. 88% of those involve ransomware. And here’s the part that should keep you up at night: 60% of small orgs don’t survive it.

The gap is real: • 51% of small businesses have zero cybersecurity measures • Only 14% have an actual security plan • Average breach cost: $4.9 million • Median time to ransomware execution: 5 days

Here’s the thing: you’re not getting targeted because you’re big or important. You’re getting targeted because you’re easy and the payoff is predictable.

The good news? The gaps that get small orgs breached are preventable. Weak authentication, unpatched systems, excessive admin privileges. Not sophisticated stuff. Just stuff that gets skipped.

We send a weekly email on security gaps that actually matter for small orgs. Sign up: [link]

CyberSecurity SMBSecurity Ransomware SecurityNews


Style B: Sharp & Direct

Small businesses are the #1 target in 2026. Stop pretending it won’t happen to you.

43% of cyberattacks hit SMBs. 88% go straight to ransomware. 60% of small orgs don’t recover.

Why you’re the target: • 51% of SMBs have no security measures at all • 86% don’t have a real cybersecurity plan • Average breach cost: $4.9 million • You’ve got 5 days before ransomware executes

The fix is predictable: eliminate weak auth, patch systems, lock down admin privileges. SonicWall’s recent report calls these “the Seven Deadly Sins” for SMBs. Not sophisticated attack vectors. Just the gaps everyone leaves open.

60% business failure rate is too high to ignore.

We send a weekly email on what actually protects small teams from preventable breaches. Sign up here: [link]

CyberSecurity SMBSecurity Ransomware InfoSec


Style C: Data Snapshot

2026 SMB cybersecurity snapshot:

43% of cyberattacks target small businesses 88% of SMB breaches involve ransomware 60% of affected small orgs go out of business 51% of SMBs have zero cybersecurity measures 14% have a formal security plan $4.9M average breach cost 5 days median time to ransomware execution

Which is why this matters: you’re not a secondary target, you’re the primary target. And the things that get you breached aren’t sophisticated. SonicWall calls them preventable gaps: weak auth, unpatched systems, excessive privilege.

Here’s the thing: your breach rate and recovery rate are directly tied to how serious you are about basics right now.

We send a weekly email on what actually moves the needle for small org security. Sign up: [link]

CyberSecurity SMBSecurity SecurityStats InfoSec


SERVICE SPOTLIGHTS


Cybersecurity Assessment

Style A: Teaching Mode

Here’s what a real cybersecurity assessment actually finds (and what most organizations are missing).

We work through SMBs on three core areas: • What you have right now (inventory, controls, gaps); you’d be shocked how many can’t answer this • Where the actual risk sits (which gaps matter, which are noise, which are actively exploited) • What to fix first (prioritized roadmap tied to your actual threat landscape, not checkbox security)

Most assessments are compliance theater: “Here’s your report.” Ours are actionable. We tell you what matters, why it matters, and how to fix it without blowing your budget.

Which is why: you can’t secure what you don’t understand. And most small orgs understand about 40% of their actual surface.

Sign up for our weekly email; we dive into how assessments work and what to look for: [link]

CyberSecurity SecurityAssessment SMBSecurity GovernanceMatters


Style B: Problem-Focused

Most SMB security assessments are useless because they don’t tell you what actually matters.

Here’s what we do differently:

We find the three things that matter right now. Not the 47 things your checklist demands. The three things that, if exploited, tank your organization.

Weak auth. Unpatched systems. Excessive privilege. That’s almost always the answer. And yeah, you probably know about them. But knowing and fixing are different.

An assessment worth doing: • Builds a threat picture specific to your organization (not generic) • Prioritizes fixes by actual risk, not compliance checkboxes • Gives you a roadmap you can actually execute • Doesn’t leave you with a 200-page report that collects dust

Let’s face it: you need to know your actual gaps before you can fix them. And you need to know which gaps matter first.

We send a weekly email on security gaps that actually move the needle for small orgs. Sign up: [link]

CyberSecurity SecurityAssessment RiskManagement SecurityLeadership


Style C: Tangible Outcomes

A cybersecurity assessment should answer one question: what do we actually need to fix?

Here’s what we look at: • Your current inventory and controls (what do you actually have, what’s configured wrong) • Your active threat landscape (who’s targeting your sector right now, what’s being exploited) • Your gaps in the context of your actual risk (not checkbox security, actual exploitable gaps) • Your roadmap (prioritized, budget-aware, executable)

Most assessments stop at inventory. Ours stop at clarity.

Which is why: small orgs don’t need another compliance report. You need to know exactly what breaks you and how to fix it first.

We send a weekly email on what actually protects small teams. Sign up here: [link]

CyberSecurity SecurityAssessment SMBSecurity GovernanceMatters


Disaster Recovery Verification

Style A: Wake-Up Call

Your disaster recovery plan is probably broken. And you won’t find out until you need it.

Here’s the thing: most organizations have a DR “plan” that’s actually just documentation no one’s tested. So when ransomware hits or a data center fails, you’re improvising.

DR verification is simple in concept: we actually test it. Under realistic conditions. Without shutting down production.

What we check: • Backup integrity (can you actually restore from what you have) • Recovery time (is 5 days realistic or are you hoping) • Runbook accuracy (does your documented recovery process actually work) • Communication gaps (does your team know what to do when it’s live)

Which is why: 60% of small orgs don’t survive a major incident. Most of them had a “plan” that didn’t work when it mattered.

We send a weekly email on what actually keeps small orgs alive during incidents. Sign up: [link]

CyberSecurity DisasterRecovery SMBSecurity BusinessContinuity


Style B: Direct & Practical

Your backups might not work. You just don’t know yet.

Most SMBs have disaster recovery documentation that’s never been tested. Which means when you need it, you’re discovering problems in real time while your business is down.

We run realistic DR verification: • Test backup restoration (from cold storage, from cloud, from tape) • Validate recovery time estimates against reality • Walk through your runbook to find what’s missing • Check that your team actually knows what to do

The result: you know exactly how long recovery actually takes, where the process breaks, and what you need to fix before disaster hits.

Which is why this matters: 60% of small orgs don’t make it past a major incident. Most had backups. They just couldn’t restore them fast enough.

We send a weekly email on what protects small teams through actual incidents. Sign up: [link]

CyberSecurity DisasterRecovery BusinessContinuity SMBSecurity


Style C: Outcome-Focused

Disaster recovery verification: the difference between a plan and something that actually works.

Here’s what we do: • Test your backups under realistic conditions (not just “restores exist”) • Measure actual recovery time (not your hope) • Walk the entire runbook start to finish (find what breaks before it matters) • Validate that your team understands their role (no improvisation during an incident)

Most small orgs discover their DR plan is broken during an actual incident. That’s too late.

Which is why: testing is cheap. Recovery from a botched restoration is not.

We send a weekly email on what actually keeps small teams running through disruptions. Sign up: [link]

CyberSecurity DisasterRecovery BusinessContinuity RiskManagement


TIMELY ALERTS


Citrix NetScaler Vulnerability (CVE-2026-3055)

Style A: Urgent + Helpful

Citrix NetScaler vulnerability is actively exploited. CVE-2026-3055, CVSS 9.3. If you’re running it, patch this week.

Here’s what you need to know: • Critical flaw being actively exploited since March 27 • CVSS score of 9.3 means “patch now, not later” • NetScaler is often your internet-facing edge device (attackers see it first) • Patch is available; exploitation is active

What to do:

  1. Check if you’re running NetScaler (ask your IT person if you’re not sure)
  2. Get the patch tested in staging this week
  3. Schedule production deployment before end of week
  4. Verify it deployed successfully

Which is why: active exploitation means attackers are looking for unpatched instances right now. You’re on a timer.

We send a weekly email on threats that need immediate attention. Sign up: [link]

CyberSecurity SecurityAlert CVE PatchNow NetScaler


Style B: Matter-of-Fact

Citrix NetScaler vulnerability CVE-2026-3055 is actively exploited. CVSS 9.3. Patch available. Deploy this week.

Details: • Flaw: critical remote code execution vulnerability • Exploitation: active since March 27 • Impact: your NetScaler is your edge; compromised edge means full network access • Status: patch released; deployment is your responsibility

If you’re running NetScaler and haven’t patched, you’re in scope for active attacks.

Action items: get the patch into staging, test it, deploy to production before end of week.

This is one of those “not optional” updates.

We send a weekly email on threats that demand immediate action. Sign up: [link]

CyberSecurity SecurityAlert CVE PatchNow


Financial Services Under Siege: What SMBs Should Do This Week

Style A: Context + Action

If you work in financial services, payments, or energy trading right now: you’re actively targeted. Here’s what to do.

Iranian cyber groups are actively hunting financial infrastructure. 245% increase in credential harvesting, reconnaissance, and DDoS setup. Regulators are issuing warnings. This isn’t theoretical.

Your action items this week: • Verify MFA (Multi-Factor Authentication) is enforced on all admin accounts (no exceptions) • Check for credential reuse across cloud services (AWS, Azure, etc.) • Review admin privilege assignments (can you justify what each person has) • Enable active monitoring or threat detection (you can’t defend what you don’t see)

Here’s the thing: you don’t need perfect security this week. You need real MFA, no credential reuse, and visibility into admin activity. That closes 80% of the attack surface these groups exploit.

We send a weekly email on what actually protects financial teams right now. Sign up: [link]

CyberSecurity FinancialServices ThreatIntel SecurityAlert


Style B: Direct + Tactical

Financial services, payments, energy: you’re being actively targeted this week. Here’s your to-do list.

245% spike in credential theft attempts. Active scanning of cloud infrastructure. Regulators warning of increased cyber risk. This is happening now.

Do these things this week:

  1. Enforce MFA on every admin account (no password-only logins)
  2. Audit credential reuse (if your cloud admin is your email admin is your database admin, you’ve exposed)
  3. Review admin privileges (lock down excessive access)
  4. Turn on active monitoring (you’re only safe if you can see intrusions)

Let’s be frank: you’re in scope for active attacks. The gap between discovering you’ve been compromised and admitting it to regulators is getting smaller.

We send a weekly email on threats that directly impact financial organizations. Sign up: [link]

CyberSecurity FinancialServices SecurityAlert Compliance


REFERENCE

Hashtag Quick-Reference

News Sources to Monitor Weekly

  • Unit42 (Palo Alto Networks): unit42.paloaltonetworks.com
  • The Hacker News: thehackernews.com
  • CISA Advisories: cisa.gov
  • SonicWall Reports: sonicwall.com
  • BrightDefense Breach List: brightdefense.com
  • SecurityWeek: securityweek.com
  • Banking Dive: bankingdive.com

Pro Tip: Batch-write Tuesday roundups on Monday evening when the week’s news has settled. Use the template structure, swap in fresh stats, and pick a CTA from the library. Should take 15-20 minutes once the rhythm is established.