Necroprancer

Mara Bell was twelve the summer the bluegrass turned silver in the mornings.

At dawn, the fields around her family’s farm in Ashbourne, Kentucky, seemed to hold their breath. Mist lay low over the paddocks, the fences shone with dew, and the stables smelled of clover hay, leather, and warm animal sleep. Beyond the barns, the training track curved like a ribbon through the rolling hills. Everyone in Ashbourne spoke in the language of horses. They spoke of bloodlines and stride length, of weather and luck, of the Derby as though it were not merely a race but a season of the soul.

Mara belonged to that world as naturally as a foal belongs to spring.

She was slight, serious-eyed, and more comfortable in boots than in church shoes. Her hair was always escaping its braid, and there was nearly always dirt on her hands. She talked less to people than most girls her age, but that was only because she never lacked conversation. She had Comet.

Comet was a rangy chestnut colt with a white blaze down his face and a habit of turning one ear toward Mara whenever she spoke, as though weighing her words. He had been born in a storm behind the east stable, and Mara had been there with a lantern, her father, and a blanket too big for her arms. From that night on, the two of them had belonged to each other.

She read to him from borrowed library books while he chewed hay. She raced him barefoot along the fence line when he was young enough to be foolish and she was young enough to think herself faster. She told him her secrets into the velvet hollow behind his jaw. When her mother died of fever, it was Comet who stood still and breathing beside her while the adults spoke in hushed voices inside the house.

By the time Mara was sixteen, Comet had grown into something beautiful and dangerous to behold. He moved with a floating ease that made seasoned trainers stop mid-sentence. He had long legs, a deep chest, and eyes bright with a kind of cleverness that made him seem almost human. Mara’s father called him the best horse ever born on their land.

“You keep dreaming too big,” he told her one evening, leaning on the paddock fence as Comet galloped the perimeter in the last gold light. “The Derby’s for men with money.”

Mara kept her eyes on Comet. “Then money ought to be worried.”

Her father laughed, but softly, because even he heard it in the colt’s stride: the promise of thunder.

That autumn, the first frost came early.

Mara found Comet at sunrise.

He lay in the back corner of his stall, still and wrong in a way that shattered the world before she even touched him. One foreleg was twisted beneath him. His eyes were open, reflecting the pale light from the stable door. The feed bucket stood untouched. On the packed dirt floor, half-buried in straw, Mara saw the dark shape of the snake. Copperhead.

Her scream brought the whole farm running.

The veterinarian arrived too late to matter. So did the neighbors. So did prayer. Nothing helped. Comet was dead, and the word seemed too small, too flat, too ordinary for what had been taken.

They buried him on the hill beyond the north pasture, beneath the old sycamore where he had liked the shade in summer. Mara stood at the grave until long after the others had gone. Wind moved through the branches above her. Somewhere in the distance, another horse whinnied, and the sound made the emptiness in her widen into something cold and bottomless.

For weeks she scarcely spoke. She stopped riding. She stopped reading. She wandered the farm like a sleepwalker, pausing outside Comet’s empty stall as though he might yet step out and nudge her shoulder for an apple.

Grief, in Ashbourne, was expected to soften into memory. Mara’s did not. It hardened.

One rainy evening, while searching the attic for an old saddle blanket she could not explain wanting, she found a cedar trunk tucked under a torn quilt and a cracked portrait of an unsmiling woman in black riding clothes. The trunk belonged, according to the brass plate, to her great-great-grandmother Lenore Bell.

Inside were books.

Not horse manuals or farm ledgers, but volumes bound in flaking leather and linen, their pages crowded with diagrams, marginal notes, lunar tables, and strange symbols drawn with a steady hand. There were titles in Latin and French, and others handwritten on the spines:

On the Vital Principle
Correspondences of Bone and Star
The Green Doctrine of Return
A Practical Index of Sympathetic Reanimation

Mara should have been frightened.

Instead, she felt something she had not felt since Comet died.

Hope.

At first, she read without understanding. The books spoke of life not as a candle extinguished, but as a pattern disturbed. They described the body as an instrument and the soul as resonance. Death, according to Lenore Bell’s notes, was not always an ending. Sometimes it was a severing that could, under certain conditions, be mended.

There were rules. There were prices. There were warnings written in the fierce slant of someone who had learned them firsthand.

Nothing true returns unchanged.

Mara read by lantern after midnight. She copied symbols until her fingers cramped. She studied anatomy from veterinary texts and astronomy from almanacs. She learned the names of herbs, minerals, old stars, and older principles. She memorized the hours at which the veil between motion and stillness was said to thin. She discovered that “occult” did not mean foolishness in those books. It meant hidden. Obscure. Knowledge tucked behind the ordinary world like a second room behind a wall.

Winter passed. Then spring.

Her father thought she was grieving in her own way. The townspeople thought she had become odd. They were right.

On the first new moon of April, Mara climbed the hill with a satchel, a spade, and Lenore Bell’s journal. The sycamore branches clawed at a cloudless sky. The earth over Comet’s grave had settled.

Her hands shook as she worked.

By midnight she had laid out the circle exactly as the journal prescribed: iron nails at the cardinal points, salt threaded with crushed rosemary, a bridle ring at the center, and on a linen cloth the things that had belonged to Comet in life, a lock of mane, a shoe, a ribbon from his halter, and the applewood brush she had used on him since he was a colt.

The journal required a witness-bond, a heart-pledge, and a living name freely given.

Mara knelt in the damp grass, dirt on her face, hair falling loose.

“I know your name,” she whispered into the dark. “I have always known it.”

She cut her palm with the edge of a farrier’s blade and let three drops fall on the bridle ring.

Wind rose.

Not ordinary wind. This came from nowhere she could point to. The salt hissed. The sycamore leaves turned their pale undersides. The lantern flame burned green, then white, then vanished entirely.

Mara began the invocation.

The words were not dramatic. They were precise. They sounded less like prayer than mathematics spoken to the bones of the world. She recited correspondences of marrow and memory, of hoofbeat and heartbeat, of loyalty as a tether stronger than soil. The ground beneath her hands trembled. The iron nails rang softly as if struck.

Then there came a sound from the grave.

A thud.

Another.

The earth heaved.

Mara should have run. Every warning in the journal said fear would break the bond, and still terror knifed through her as the soil split and a shape forced upward from the dark. First a foreleg, then another, then the long blaze of a skull made terrible by moonless light and wet dirt.

Comet rose.

He stood within the ruined grave, breathing no breath Mara could see. Clods of earth slid from his flanks. His coat, once chestnut bright, was now dark as old mahogany, threaded here and there with a faint silver sheen. His eyes were not dead, as she had feared. They were deeper than before, black and lucid and full of a patient, uncanny fire.

“Mara,” said a voice in her mind, not in words exactly, but in recognition so complete it nearly stopped her heart.

She wept then, helplessly, and stepped inside the broken circle to throw her arms around his neck.

He was cold.

He was real.

From that night on, the world became a stranger place, but not an emptier one.

Comet returned to the stable before dawn under a tarpaulin and silence. Mara kept him hidden at first, in the old west barn no one used. She fed him little, because he seemed to require little. He drank sometimes, not always. He did not sleep, at least not as horses do. But he remembered everything. He bowed his neck when she approached. He stamped impatiently when she made him wait. And when she led him out under the stars, his hooves struck sparks from stone.

It soon became clear that Lenore Bell’s warning had been true. He was changed.

Comet no longer tired.

He no longer startled.

He ran with a steadiness beyond flesh, as though the earth itself lent him motion. At full gallop, he seemed less to cross the ground than to command it. Yet there was something else too, some shadow at the edge of him. Dogs whimpered when he passed. Birds went silent in the hedgerows. Other horses rolled their eyes and pulled against their reins.

Mara should have understood what that meant.

Instead, she saw only what she had regained.

By late summer, rumors had begun. A new horse had appeared on the Bell farm, people said. A magnificent animal. Odd-tempered, perhaps, but fast. Mara’s father, pressed by bills and dazzled by possibility, entered Comet under his old name in the autumn trials. He did not ask how Mara had restored him to condition after burial. Adults often mistake impossibility for youthful resilience when they want very badly to believe.

Comet won the first trial by six lengths.

Then the next by eight.

Jockeys complained that running against him felt wrong. Trainers crossed themselves. One newspaper called him “the grave-dark wonder of Ashbourne.” Another simply called him unbeatable.

Mara rode him in secret at night and trained him at dawn. As the Derby approached, so did the thing she had refused to name. Comet was with her, yes, but not wholly in the old way. Sometimes she woke to find him standing outside her bedroom window, silent as a carved thing, though the stable door remained locked. Sometimes his thoughts brushed hers with a depth that frightened her, not because they were cruel, but because they were no longer entirely horse-thoughts. The ritual had returned him, but it had also opened him.

And through that opening, something older looked back.

Three nights before the Derby, Mara went again to the attic and reread Lenore Bell’s final pages. There, at the bottom of one water-stained sheet, she found a line she had somehow missed:

What returns through love may remain through will, but what remains through will must someday choose its own master.

Mara sat very still in the lantern light.

Below, in the yard, she heard Comet paw once against the ground.

The Kentucky Derby dawned bright and cool, all banners, roses, brass music, and crowds drunk on spectacle. Churchill Downs shimmered in the spring sun. Wealthy men smiled into cameras. Ladies tilted bright hats. Bookmakers shouted odds. The infield roared like a living sea.

Mara stood beside Comet in the paddock tunnel and laid a hand against his neck.

Everyone stared.

At the horse, because he was magnificent.

At the girl, because she insisted on riding him herself.

She had fought for that much and somehow won. Perhaps because no one could deny that Comet answered to her alone. Perhaps because the Bell farm had become the story people wanted, the grief-struck girl and the resurrected champion, though only Mara knew how literal that story truly was.

The bugle sounded.

The gates opened.

They flew.

Horses thundered from the line, but Comet moved among them like an omen. First curve, backstretch, final turn, he devoured ground. Mara felt his power gather beneath her, immense and tireless, and with it a rising exultation, dangerous as lightning. The crowd became a blur. Mud struck her boots. Wind tore tears from her eyes.

They took the lead.

Then something happened.

As they drove into the final stretch, necks and hooves and noise all exploding around them, Mara felt Comet reach for something beyond the race. Beyond her. The bond between them strained like a rope in fire. His speed sharpened into something inhuman. For one terrible instant she understood that if she urged him on, if she let this thing inside him fully loose, he would win not as a horse wins but as a force does, absolute and monstrous and undeniable.

He would cross the line first.

And never belong to the world again.

Mara saw in a flash the years ahead: trophies, fear, whispers, and herself clinging to a miracle she had mistaken for love. Keeping him because she could, not because she should.

“No,” she said aloud, though the crowd swallowed it.

Comet heard.

Not with ears. With the bond.

She loosened the reins.

Not to send him faster, but to release him.

“I loved you alive,” she thought at him with all the fierce grief and gratitude in her. “I will not keep you unalive.”

The force inside him reared against the choice. For half a heartbeat the world seemed to split. His body shone with that strange silver fire Mara had seen on the hill. The air around them went cold. Spectators gasped without knowing why.

Then Comet yielded.

Not to the magic.

To Mara.

He eased.

Just enough.

One horse passed them, then another by half a length. Comet crossed the finish third, still glorious, still impossibly strong, but no longer straining toward that dreadful beyond.

The crowd roared anyway.

Mara bent over his neck, sobbing into his mane as photographers flashed and officials shouted and the Derby crowned another winner.

That night, while the city still celebrated, Mara led Comet away from the stables to a quiet field beyond the track. The moon was nearly full. The grass whispered around their legs.

He stood facing her, calm and dark and beautiful.

“I know,” she said.

His thoughts came softly now, more horse than shadow. More Comet than whatever had tried to wear him.

Home, he seemed to say.

“Yes.”

Mara drew from her pocket the bridle ring from the first ritual and the page from Lenore Bell’s journal on which she had written, in her own hand, a second working. Not reanimation. Release.

This one required no blood.

Only consent.

She placed her forehead against Comet’s and spoke the words. They were simpler than the first rite. Gentler. They did not call anything back. They only opened a door.

The silver fire came again, but warm this time, like sunrise through closed eyelids.

Comet touched his nose to her shoulder.

Then he was gone.

Not vanishing like smoke. Not collapsing like a puppet with cut strings. He simply ceased to be where he had been, as naturally as a breath leaving the body. The field remained. The moon remained. Mara remained, with tears on her cheeks and one chestnut hair caught on her sleeve.

Years later, people still told the story of Mara Bell and Comet. Depending on who told it, they had nearly won the Derby, or ought to have, or were cheated by fate. Some swore Comet had glowed in the final stretch. Some said Mara had pulled him on purpose. Some said love made girls foolish. Others said it made them brave.

Mara grew up and became many things, a trainer, a scholar of hidden traditions, a woman who understood that not all lost things are meant to be reclaimed. She kept Lenore Bell’s books, but she never again used them to drag the dead into the light. Instead she studied the old sciences to heal where she could, to ease fear where she found it, and to honor the thin, mysterious border between holding on and letting go.

And every Derby Day, before the crowds gathered and the bugle sang, Mara walked alone to the rail in the pale morning.

Sometimes, when mist lay low over the track and the bluegrass shone silver, she thought she heard hoof-beats beside her, light and certain and dear.

She never turned to look.

She did not need to.

She smiled into the dawn and said, “Good morning, Comet.”

And somewhere beyond sight, in whatever field waits for the well-loved dead, something ran.

 

Happy St. Patrick's Day!

 Happy St. Patrick's Day! I made this today:

=============================================================

Medieval Corned Beef
British Isles - Medieval 
(Honey-basted roasted corned beef.)
City/Region: Ireland 
Time Period: c. 1100
URL: https://www.tastinghistory.com/recipes/medievalcornedbeef


Corned beef’s popularity fell in medieval Ireland because most of the good corned beef was sent overseas to England.  Pork was cheaper to raise, so many ate bacon and cabbage until the Irish Potato Famine, when many immigrated to America. The neighborhoods where they tended to move to were serviced by Kosher butchers, who didn’t have any bacon, but did have plenty of corned beef. This recipe is derived from a poem written around 1100, which describes how corned beef was prepared. The main difference between this medieval preparation and modern versions is the honey. The combination of corned beef's saltiness and honey's sweetness is so wonderful. Delicious!

“Tender corned beef…and honey in the comb, and English salt…He rubbed the honey and the salt into one piece after another.” 
— Aislinge Maic Con Glinne (The Vision of Mac Con Glinne), c. 1100

Ingredients:

4 lbs (2 kg) corned beef brisket (my brisket was only 3 pounds...)
1/4 cup (85 g) honey
1/2 teaspoon salt
(I added 1 shot of Jamison's Irish Whiskey because...)

Instructions:
1. Preheat the oven to 325°F (165°C).
2. In a large pot, cover the corned beef with water and bring to a boil. Boil for 1 minute, then drain. Repeat at least once. This process will help reduce the corned beef's saltiness. After you’ve boiled the corned beef at least twice, place it on a large piece of foil.
3. Mix the salt and the honey, then brush it generously all over the corned beef. Wrap the corned beef in the foil and place it on a baking sheet or roasting pan. Roast in the oven for 1 hour per pound.
4. 30 minutes before the corned beef is done, open the foil and raise the temperature of the oven to 400°F (205°C) to brown the top.
5. Slice and serve it forth with Cabbage Pottage.

=============================================================
Cabbage Pottage
British Isles - Medieval 
(Cabbage cooked with leeks and onions.)
City/Region: Ireland | England
Time Period: 14th Century
URL: https://www.tastinghistory.com/recipes/cabbagepottage


“Caboches in potage. Take caboches and quarter them, and seeth them in gode broth with oynouns mynced and the whyte of lekes slit and carved small”      
— Curye on Inglysch, 14th Century

Finding a historical recipe from Ireland is really hard, and finding a medieval Irish recipe is basically impossible. I started with a medieval English recipe from a few hundred years after the corned beef description. I adjusted it to match the ingredients we know were available in Ireland around 1100. The cabbage pottage is simple to prepare and has a mild flavor, though there is a touch of heat from the onions and leeks. The simplicity of the dish pairs perfectly with the complex Medieval Corned Beef. 

Ingredients:
 1 large head of cabbage, quartered
 1 large onion, chopped fine
 2 leeks, sliced into half rings
 2 cups beef broth (I ended up using 4 cups...)
 1 teaspoon salt
 1 teaspoon pepper, optional

Instructions:

1. Leeks can have dirt and silt in them, so swish the sliced leeks in a large bowl of water to clean them.
2. Combine the vegetables in a pot and sprinkle them with the salt and optional pepper.
3. Pour in the beef broth and bring it to a boil. Reduce to a simmer and cover. Cook for 20 to 30 minutes.
4. Serve it forth with Medieval Corned Beef.

=============================================================



Graduation Memento!

 
I got this in the mail yesterday. A pretty cool memento!

Ode to Cybersecurity



The History of “Cyber”: How an Ancient Word Shaped the Digital Age

 

What’s in a Word? The Origin of “Cyber”

If you spend any time in the worlds of technology, security, or defense, you’ve probably noticed that cyber has become the ultimate prefix. We hear about cybersecurity, cybercrime, cyber operations, and even cyber cafés. But where did this little word actually come from, and why has it stuck around?

Let’s take a quick journey through history.


From Ancient Greece to Modern Tech

The story begins in ancient Greece. The word κυβερνήτης (kybernētēs) meant helmsman or steersman—someone who guides a ship. That idea of steering or governing is at the root of the modern term.

Fast-forward to the 20th century, when American mathematician Norbert Wiener drew on this concept. In 1948, he published Cybernetics: Or Control and Communication in the Animal and the Machine. For Wiener, cybernetics was the science of control systems, feedback loops, and communication, whether in a living brain or a mechanical device. The Greek “steersman” was now steering machines and information.


Cybernetics Meets Computing

As computing matured in the 1960s and 70s, the language of cybernetics seeped into computer science and artificial intelligence. Researchers began using “cyber” as shorthand for anything involving machines, systems, and information flow.

It was a technical term, but one waiting to jump into popular culture.


Enter Cyberspace

The big leap came in 1984 when science fiction author William Gibson published Neuromancer. In it, he described cyberspace as a “consensual hallucination” shared by millions—a digital world inside computer networks.

That vision stuck. By the 1990s, as the internet went mainstream, “cyber” became glued to nearly every online activity: cyber cafés, cybersex, cybercrime, and more. What had once been a mathematical idea now belonged to pop culture.


Today’s “Cyber”

Today, “cyber” has narrowed its focus. Governments, businesses, and security professionals use it mostly to describe the digital domain—especially the threats and defenses around it. For example:

  • Cybersecurity: protecting systems, networks, and data

  • Cyber operations: digital activities carried out by militaries or governments

  • Cyber threats: malicious activity in the online space

In other words, “cyber” is shorthand for the intersection of technology, information, and control—exactly where it started back with Wiener.


Why It Matters

Words carry history. Understanding where “cyber” comes from helps us see that our conversations about digital safety, control, and communication aren’t entirely new—they’re rooted in centuries-old ideas about guidance, governance, and steering through uncertainty.

So next time you hear “cyber,” remember: it’s not just jargon. It’s a word with a journey—one that began on the decks of Greek ships and found its way into the heart of our digital age.

Ode to Linux

A techie with skills so supreme,
Preferred Linux to Windows' regime.
With sudo and bash,
He solved every crash,
And his uptime was always a dream.

Echoes in the Storm

In the quiet corners of his mind,
A storm swirls, leaving peace behind.
Thoughts race like leaves in a restless breeze,
Yet he's anchored, trapped, on shaking knees.

Loneliness whispers in every sound,
A hollow echo that knows no bound.
The world moves on, but he's out of sync,
Drowning in the chaos where others think.

A spark of hope, a fleeting flame,
Extinguished quickly, the dark's to blame.
Focus shattered, time slips away,
Another lost hour, another gray day.

And yet, within this shadowed strife,
Flickers a will, a thread of life.
Though heavy the burden, deep the despair,
A quiet strength reminds he's still there.


 

BSIT400 - Week 12 Posting - Exploring the Benefits of Infrastructure as Code (IaC)

Infrastructure as Code (IaC) manages IT infrastructure through configuration files, allowing teams to automate and standardize deployments rather than manual processes. In IaC, administrators define infrastructure needs—like servers, networks, and storage—using code, transforming infrastructure management into a process similar to software development (Microsoft, n.d.).

One of IaC’s core benefits is consistency. With every piece of infrastructure described in the code, deployments across environments, such as development, testing, and production, remain consistent. This approach reduces “configuration drift,” which often results from manual changes that complicate troubleshooting and system management over time. When environments match in configuration, applications become more reliable and supportable (Red Hat, n.d.).


IaC also enhances
efficiency and speed. With tools like Terraform, Ansible, or AWS CloudFormation, IaC enables quick infrastructure deployment and on-demand scaling. Automated deployments reduce setup time and minimize human error, allowing faster, more reliable updates. This adaptability improves cost efficiency as resources can be scaled up or down according to demand, optimizing infrastructure expenses (HashiCorp, n.d.).


Furthermore, IaC fosters
collaboration by allowing infrastructure configurations to be stored and versioned in repositories, similar to software code. Teams can track changes, roll back to previous configurations if needed, and test updates before applying them to production. By treating infrastructure as code, IaC promotes faster iteration, fewer errors, and greater scalability, aligning IT practices with today’s demand for agility (Amazon Web Services [AWS], n.d.).


References

Amazon Web Services. (n.d.). What is infrastructure as code? Retrieved from https://aws.amazon.com/what-is/infrastructure-as-code/

HashiCorp. (n.d.). Infrastructure as Code with HashiCorp Terraform. Retrieved from https://www.hashicorp.com

Microsoft. (n.d.). Overview of infrastructure as code. Retrieved from https://docs.microsoft.com

Red Hat. (n.d.). What is infrastructure as code? Retrieved from https://www.redhat.com 



A "wrap-up" of my Blogging experience:

  • What did you find enjoyable or not about this assignment?
    • I enjoy the creative writing involved in making these posts.
  • Was it helpful to you in your current job?
    • My current job title is "Principal Systems Engineer," and I've been in IT for 40 years. No, not really.
  • Can you see yourself Blogging in the future when it isn't required for an assignment?
    • Yes, I can. Researching a subject and creating something people will want to read is fun.
  • Can you see this ability as desirable for a company, giving you more weapons in your arsenal and making you a more attractive hire?
    • No, not at all. No company has ever asked me to produce any writings other than technical documentation.

BSIT400 - Week 11 Posting - Understanding RTO and RPO: Key Metrics for Effective Disaster Recovery Planning

When organizations plan for disaster recovery, two critical metrics guide the process: Recovery Time Objective (RTO) and Recovery Point Objective (RPO). Although often mentioned together, RTO and RPO serve different purposes in helping a business recover from unexpected disruptions. Both metrics help define acceptable downtime and data loss levels, allowing organizations to create a recovery strategy that meets their operational needs and budget.

The Recovery Time Objective (RTO) refers to the maximum time a business can tolerate being offline after a disruption before it starts to experience serious consequences. RTO answers, "How long can we afford to be down?" For example, if a company has an RTO of four hours for its email system, it must restore email access within four hours to avoid significant impacts on business operations. RTO helps businesses prioritize which systems and services need to return to service quickly to minimize financial loss or operational setbacks.


On the other hand, the
Recovery Point Objective (RPO) focuses on data loss tolerance. RPO determines how much data a business can lose by setting a time limit for data recovery. For example, if an organization has an RPO of one hour, it means that, in the event of a failure, data recovery should bring the system back to a state no older than one hour before the incident. This requires frequent data backups or replication. Together, RTO and RPO are essential in disaster recovery planning. RTO addresses downtime limits, while RPO manages data loss limits, helping organizations create balanced recovery strategies based on their needs.

BSIT400 - Week 10 Posting - Data Obfuscation 101: Understanding Encryption and Tokenization in Today’s Digital World

In today’s digital world, data breaches are becoming more sophisticated, and protecting sensitive information is more crucial than ever. This is where data obfuscation techniques like encryption and tokenization come into play. These methods serve as essential shields to keep personal, financial, and business-critical data safe from prying eyes.


Encryption
is the most well-known method. It converts readable data (plaintext) into a scrambled format (ciphertext) using algorithms and keys. Only someone with the proper key can decrypt and make sense of it. Encryption secures everything from private messages to banking information, whether the data is being stored or transferred. The catch? The safety of encrypted data heavily depends on managing and protecting those keys. If a key falls into the wrong hands, the data becomes vulnerable.


Tokenization
, on the other hand, works differently. Instead of scrambling data, it replaces sensitive information with non-sensitive placeholders called tokens. For example, your credit card number could be swapped with a random token that maps back to the actual number in a secure vault. This method is beneficial for payment processing, as even if a hacker gets a hold of the token, it’s worthless without access to the original data.


While both techniques enhance security, they have different strengths. Encryption is versatile but requires diligent key management, while tokenization is ideal for safeguarding specific data elements, like credit card numbers, in compliance-heavy environments. Companies often combine both methods to create robust data protection strategies that balance performance, security, and regulatory needs.


Understanding these techniques is critical to securing our digital world, with cyber threats rising. Whether you’re an IT professional or a concerned internet user, knowing how your data is protected can give you peace of mind in our increasingly connected world.

BSIT400 - Week 9 Posting - Safeguarding Digital Trust: The Crucial Role of Key and Certificate Management

Key and certificate management are critical components of modern cybersecurity. Keys, whether for encryption or signing, and digital certificates, which authenticate identities online, must be managed appropriately to ensure the security and integrity of communications and data in any organization.
Proper key management ensures that encryption keys are stored securely, regularly rotated, and used appropriately to protect sensitive data. If encryption keys are compromised or mismanaged, encrypted data becomes vulnerable to unauthorized access, undermining the entire security system. Managing keys also includes ensuring they are securely shared between parties, preventing them from being intercepted during transmission.

On the other hand, certificate management involves issuing, renewing, and revoking digital certificates that verify the authenticity of websites, applications, and users. Secure communication channels, such as those established using SSL/TLS, can be compromised without well-maintained certificates. Expired or invalid certificates can lead to security warnings or open the door to man-in-the-middle attacks where attackers impersonate legitimate entities.

Both key and certificate management are essential for maintaining the trustworthiness of systems and data exchanges. Without effective management, businesses can face serious risks, including data breaches, loss of customer trust, and non-compliance with security regulations, ultimately threatening their overall security posture.

Reference

What is certificate management?: SSL/TLS Certificate. Encryption Consulting. (2024, September 19). https://www.encryptionconsulting.com/education-center/what-is-certificate-management/


 

Whispers at the Door

The night is still, yet something feels amiss,
As children come for treats and playful bliss.
I smile and drop the candy in their bags,
But shadows stretch, and time begins to lag.

Each face I see, a mask, but not quite right,
Their hollow eyes reflect the fading light.
They shuffle close with whispers soft and cold,
My hands grow numb, the candy turns to mold.

They’re not the ones I thought I'd see tonight—
Too late I shut the door against the night.

BSIT400 - Week 8 Posting - Cloud Security Practices

Cloud security is a growing concern, and effective troubleshooting methods are essential for keeping systems safe. One popular methodology is Root Cause Analysis (RCA). This approach involves identifying the underlying cause of an issue to prevent it from happening again. For example, if a cloud server experiences unauthorized access, you must investigate how it occurred and address the vulnerabilities that allowed it. Penetration testing is another valuable strategy. By simulating attacks, organizations can discover weaknesses in their cloud infrastructure before malicious actors do.


The
Six-Step Troubleshooting Process is widely used for resolving cloud security issues. This process involves identifying the problem, gathering data, forming a hypothesis, testing the hypothesis, implementing a solution, and monitoring results. This method ensures that all angles are covered when addressing security incidents. Another essential tip is to monitor logs and alerts constantly. Cloud environments provide rich logging data, which can help administrators detect suspicious activity early. Regular audits of user permissions, data encryption methods, and security protocols also play a vital role in maintaining cloud security.

Maintaining cloud security requires a combination of proactive and reactive strategies. Troubleshooting security issues effectively involves thorough investigation, regular testing, and constant vigilance.

For further reading on cloud security strategies, check out the IBM Cloud Security webpage (IBM, What is cloud security? 2024), which provides an overview of cloud security best practices, including methods for identifying and mitigating risks and tips on maintaining security in cloud environments.

 

Reference:

IBM. (2024, October 1). What is cloud security? https://www.ibm.com/topics/cloud-security




 

 

BSIT400 - Week 7 Blog Posting - Article Review

For this weeks blog entry, I have decided to provide a review of an interesting article titled "What's the difference between cloud computing and colocation?", written by Alex Carroll and published on the Lifeline Data Centers website at https://lifelinedatacenters.com/colocation/whats-the-difference-between-cloud-computing-and-colocation/. 

The article offers a clear comparison between cloud computing and colocation, two approaches businesses can use for data storage and computing power. Cloud computing provides access to virtualized resources over the internet, making it ideal for companies looking for scalability without investing in physical infrastructure. Conversely, colocation allows businesses to rent space within a data center to house their own servers, providing more control over their hardware but requiring higher upfront investments.

The article makes a strong case for cloud computing's flexibility, especially for startups and smaller businesses that need scalable solutions without the overhead of managing physical servers. By offering virtualized environments, cloud computing reduces the cost of entry and ongoing maintenance. It also simplifies scaling up or down based on the business's needs, a significant advantage in a rapidly evolving market.

In contrast, the article highlights the advantages of colocation for larger companies with more specific requirements. These companies often choose colocation because it allows them to maintain greater control over their hardware and network configurations. Businesses that have invested in physical servers may find colocation a better option, as it helps ensure they meet compliance requirements while keeping their data secure in a professional data center environment.

The article provides valuable insights into how cloud computing and colocation serve different needs. While cloud computing is often favored for its ease of use and scalability, colocation remains a strong option for businesses seeking more control over their physical infrastructure. The choice ultimately depends on each business's specific needs, budget, and long-term goals.

Reference:

Carroll, A. (2017, June 12). What’s the difference between cloud computing and colocation? Lifeline Data Centers. https://lifelinedatacenters.com/colocation/whats-the-difference-between-cloud-computing-and-colocation/




BSIT400 Week 6 Posting - What is a Virtual Private Cloud?

A Virtual Private Cloud (VPC) in Amazon Web Services (AWS) allows you to create a logically isolated network within the AWS cloud, giving you control over your virtual environment. Think of it as your private data center in the cloud, where you define everything from the IP address range to how your network routes traffic.

When you create a VPC, you start by defining the IP address range for the network using CIDR (Classless Inter-Domain Routing) notation. You then divide this network into smaller sections called subnets, which can be either public or private. Public subnets can directly communicate with the internet, while private subnets stay isolated unless you specifically allow access. For example, a web server can be placed in a public subnet, and a database server can be placed in a private subnet to protect sensitive data.

Each VPC automatically comes with a default route table, which controls traffic flow within your network. You can also create custom route tables to define more specific rules. AWS provides a virtual internet gateway for public subnets to access the internet. For secure connections between your on-premises network and your VPC, AWS offers a Virtual Private Gateway, allowing you to extend your private data center to the cloud securely.

Security in a VPC is handled through Network Access Control Lists (ACLs) and Security Groups. These allow you to define which IP addresses or ranges can access specific resources in your VPC, providing a layered approach to securing your cloud infrastructure. A VPC gives you complete control over your network environment, from designing subnets to managing traffic routing, ensuring you can securely run applications in the AWS cloud.

Reference: 

Amazon. (2024). What is Amazon VPC? - amazon virtual private cloud. Amazon Web Services. https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html


 

Short Story: The Guardian of the Obelisk

Rick Mason stepped outside his small ranch house in Omaha, Nebraska, feeling the crisp autumn air bite at his skin. At 60, Rick had seen his share of mysteries—both in his time as a Master Mason and from decades of studying arcane lore and ancient symbolism. However, tonight, something different tugged at him. It wasn’t the usual chill of the Midwestern breeze; it was a feeling deep in his bones, something uncanny that had been gnawing at him all week.

Rick wasn’t just any Mason. As the current Master of his Lodge, he was well-respected in the community for his wisdom, his calm demeanor, and his ability to see past the surface of things. But even with years of experience, nothing had prepared him for the strange occurrences that had begun to plague him. His dreams had been vivid and bizarre—filled with images of an ancient obelisk hidden deep beneath Nebraska’s seemingly ordinary landscape. The dreams were so real, they were more than mere dreams—Rick knew they were something else, something calling to him.

The dreams always began the same way. Rick found himself in a cornfield, tall stalks rustling in the wind as the moon cast eerie shadows across the rows. A pathway would open up between the crops, leading him toward a colossal black obelisk, inscribed with strange symbols. He could never get too close to it; something would always wake him just before he could reach out and touch the cold stone.

Rick shook his head as he unlocked his car, trying to push the unease away. Tonight, he had Lodge business to attend to. It was the annual meeting where he, as Master, would oversee the admission of a new member—always a solemn and important affair. However, something told him that tonight’s meeting would be far from routine.

He arrived at the Lodge, a century-old building nestled between modern storefronts. The Masonic Hall had stood the test of time, a relic of an age where mystery and fraternity went hand in hand. Inside, the walls were adorned with symbols—compasses, squares, and the all-seeing eye—while the rich smell of old wood and incense filled the air. Rick took a deep breath, feeling a sense of familiarity and calm wash over him, but only for a moment. There was still that gnawing feeling of something off-kilter.

As the brethren arrived, Rick greeted each of them, shaking hands and exchanging pleasantries. Tonight, they would initiate Mark Smith, a local businessman, into the fraternity. Mark had come highly recommended, but Rick couldn’t shake the strange feeling that had settled into his bones.

As the meeting commenced, Rick took his place at the East, the seat of the Master, and began the opening ritual. The room fell silent as the members of the Lodge followed their practiced routines. But halfway through the ceremony, a strange thing happened.

The power flickered. The lights dimmed, casting long shadows across the room, and for a brief moment, Rick thought he saw the outline of the obelisk from his dream, standing in the corner of the Lodge. He blinked, shaking his head. It was gone in an instant, but his heart raced.

"Are you alright, Worshipful Master?" asked one of the brothers, concern etched in his voice.

Rick forced a smile and nodded. "I'm fine. Let’s continue."

But Rick knew he wasn’t fine. The visions were becoming stronger, more real. He glanced at Mark Sanders, who was kneeling before the altar, and felt an uneasy pull in his gut. There was something about the man that seemed… off. Not in a malicious way, but as if Sanders wasn’t entirely of this world. His demeanor was calm, almost too calm, and his eyes seemed to glow faintly in the dim light of the Lodge room.

After the meeting, Rick lingered behind while the other brothers left, unable to shake the feeling that something important was about to happen. He wandered the Lodge’s antechambers, his mind still racing with thoughts of the obelisk. What did it mean? And why was it haunting him?

As Rick approached the door to the old storage room in the back of the Lodge, a cold draft swept past him. The door creaked open on its own, revealing a space that had remained untouched for decades. Rick stepped inside, squinting in the darkness, when he noticed something unusual—a faint glow coming from behind a stack of old boxes.

His heart pounded as he moved the boxes aside to reveal what was causing the glow. There, nestled against the wall, was a strange stone tablet. It was covered in the same symbols he had seen on the obelisk in his dreams. Rick knelt down, tracing the strange inscriptions with his fingers. The tablet felt warm to the touch, as if it were alive.

Suddenly, the ground beneath Rick shifted. The walls of the Lodge seemed to bend and twist, and before he could react, Rick found himself no longer in the storage room but standing in the middle of a vast cornfield under a moonlit sky. The familiar rustling of the corn surrounded him, and in the distance, the obelisk loomed.

This time, Rick was able to move closer. He felt an invisible force guiding him toward the towering stone structure. His heart raced as he approached it, the ancient symbols glowing brighter with every step. He reached out, his fingers brushing the cold stone, and instantly, a surge of energy pulsed through him.

In a flash, visions exploded in his mind—images of long-forgotten civilizations, of beings not of this Earth, and of Nebraska as it had been centuries ago, a place of great power and mystery. The obelisk, it seemed, was a remnant of an ancient race that had once lived beneath the soil of the Great Plains. And Rick, for reasons he couldn’t yet understand, had been chosen as its Guardian.

As the visions subsided, Rick found himself standing in the cornfield once again, the obelisk towering above him. But now, it was different. Now, he understood. The obelisk wasn’t just a relic of the past; it was a beacon, a gateway to another realm—one that was trying to open.

Suddenly, a voice echoed through the night, deep and resonant.

"Rick Mason," it said, "you have been chosen."

Rick turned, searching for the source of the voice, but found nothing but darkness. His heart pounded in his chest as the voice continued.

"You are the Guardian of the Obelisk. The key to the ancient door lies within you. Protect it, for dark forces are stirring."

Before Rick could respond, the world around him shifted once again, and he found himself back in the storage room of the Lodge, the stone tablet still glowing faintly at his feet. His head spun as he tried to process what had just happened. He had seen things—impossible things—yet he knew deep in his heart that they were real.

The obelisk was not just a symbol from his dreams; it was part of something far greater, something that had been hidden beneath the soil of Nebraska for centuries. And Rick, for reasons he couldn’t yet fathom, had been drawn into its orbit.

Breathing heavily, Rick picked up the tablet and placed it carefully in a leather satchel. He had no idea what lay ahead, but one thing was clear: his life had just taken a turn into the unknown, and he was now part of a mystery that spanned time and space.

As he exited the Lodge that night, the moon hung high in the sky, casting long shadows across the quiet streets of Omaha. Rick glanced back at the Lodge, a strange mixture of dread and excitement swirling within him. He had always been a seeker of truth, and now it seemed that truth was seeking him.

The Guardian of the Obelisk had been awakened, and whatever came next, Rick knew he had a role to play.

With the tablet in hand, he started his car and headed home, knowing that the mysteries of the obelisk, and perhaps even the fate of the world, rested on his shoulders.

And this was only the beginning.

The End.